| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
MUX_CPU_LIMIT, MUX_MEMORY_LIMIT.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and memory_limit.
Default values:
openshift_logging_fluentd_cpu_limit: 100m
openshift_logging_fluentd_memory_limit: 512Mi
openshift_logging_fluentd_buffer_queue_limit: 1024
openshift_logging_fluentd_buffer_size_limit: 16m
openshift_logging_fluentd_buffer_size_limit: 1m
openshift_logging_mux_cpu_limit: 500m
openshift_logging_mux_memory_limit: 1Gi
openshift_logging_mux_buffer_queue_limit: 1024
openshift_logging_mux_buffer_size_limit: 1m
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we currently create the set of logging `DeploymentConfig`s, we
create them with zero desired replicas. This causes the deployment to
immediately succeed as there is no work to be done. This inhibits our
ability to use nice CLI UX features like `oc rollout status` to monitor
the logging stack deployments. Instead, we should can create the configs
with the correct number of replicas in the first place and stop using
`oc scale` to bring them up after the fact.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
|
|
|