openstack/openstack-helm-infra
Code Issues Proposed changes

Add Liveness Probe to Kibana Deployment

Browse Source 
This change adds a liveness probe to the Kibana deployment spec.
If multiple kibana replicas are deployed simultaniously they race
to update the .kibana index in Elasticsearch, which sometimes
results in a pod to stall without starting it's http server.

Change-Id: Ib685d738ced59df66ff3501749316a01b5cacf79
This commit is contained in:
Steven Fitzpatrick 2020-02-25 13:17:22 -06:00
parent e54f5f778f
commit 371b1cbe89
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
kibana/templates/deployment.yaml
View File

@ -71,11 +71,16 @@ spec:
ports: ports:
- name: http - name: http
containerPort: {{ tuple "kibana" "internal" "http" . | include "helm-toolkit.endpoints.endpoint_port_lookup" }} containerPort: {{ tuple "kibana" "internal" "http" . | include "helm-toolkit.endpoints.endpoint_port_lookup" }}
livenessProbe:
tcpSocket:
port: {{ tuple "kibana" "internal" "http" . | include "helm-toolkit.endpoints.endpoint_port_lookup" }}
initialDelaySeconds: 180
periodSeconds: 60
readinessProbe: readinessProbe:
tcpSocket: tcpSocket:
port: {{ tuple "kibana" "internal" "http" . | include "helm-toolkit.endpoints.endpoint_port_lookup" }} port: {{ tuple "kibana" "internal" "http" . | include "helm-toolkit.endpoints.endpoint_port_lookup" }}
initialDelaySeconds: 20 initialDelaySeconds: 20
periodSeconds: 10 periodSeconds: 30
env: env:
- name: ELASTICSEARCH_USERNAME - name: ELASTICSEARCH_USERNAME
valueFrom: valueFrom: