| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The readiness probe, as currently implemented, together with the ES
master discovery using the logging-es service, causes a deadlock on
clusters with more than one node. Readiness probe will be
reintroduced in later release.
More information in:
https://bugzilla.redhat.com/show_bug.cgi?id=1459430
|
|\
| |
| | |
logging: write ES heap dump to persistent storage
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|