f3ed56cc18
Strictly speaking, open socket doesn't mean working API. We experienced API stopped responding and the socket was still open so API was unhealthy actually but kubernetes did not restart. HTTP probe will fix this issue. Change-Id: I95bb3ad3123d8a4a784d260477f037fa5506d290 |
||
---|---|---|
.. | ||
bin | ||
configmap-bin.yaml | ||
configmap-etc.yaml | ||
daemonset-host-monitor.yaml | ||
daemonset-instance-monitor.yaml | ||
daemonset-process-monitor.yaml | ||
deployment-api.yaml | ||
deployment-engine.yaml | ||
job-db-drop.yaml | ||
job-db-init.yaml | ||
job-db-sync.yaml | ||
job-ks-endpoints.yaml | ||
job-ks-service.yaml | ||
job-ks-user.yaml | ||
job-rabbitmq-init.yaml | ||
pbd-api.yaml | ||
secret_rabbitmq.yaml | ||
secret-db.yaml | ||
secret-keystone.yaml | ||
secret-registry.yaml | ||
service-api.yaml |