Phil Sphicas 354deab382 kube-proxy: use HTTP probes instead of exec ... The existing liveness and readiness probes for kube-proxy are in need of adjustment. The current implementation is exec-based, which can be a resource concern, and is tied heavily to iptables, so is incompatible with ipvs. This change removes the exec-based liveness and readiness probes from the kube-proxy daemonset, and replaces them with HTTP probes of the healthz endpoint, following the direction that kubernetes seems to be taking.[0][1] The values.yaml interface to enable and disable the probes and set various parameters is also modified to use the helm-toolkit standard snippet.[2] Notably, the settings previously configurable under livenessProbe.config are now under pod.probes.proxy.proxy.liveness.params. 0: https://github.com/kubernetes/kubernetes/issues/81630 1: https://github.com/kubernetes/kubernetes/pull/75323 2: https://opendev.org/openstack/openstack-helm-infra/src/branch/master/helm-toolkit/templates/snippets/_kubernetes_probes.tpl Change-Id: I99ccbc2270a1f8a204417aa410868d04788dc60f		2020-05-24 07:38:55 +00:00
..
templates	kube-proxy: use HTTP probes instead of exec	2020-05-24 07:38:55 +00:00
Chart.yaml	Refactor Kubernetes Proxy Chart	2017-11-20 13:56:19 -05:00
requirements.yaml	Refactor Kubernetes Proxy Chart	2017-11-20 13:56:19 -05:00
values.yaml	kube-proxy: use HTTP probes instead of exec	2020-05-24 07:38:55 +00:00