You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Delete the flux-helm-operator pod, let it restart.
Expected behavior
I expected flux-helm-operator to retry connectivity to Kubernetes API endpoint, or to exit, or to report unhealthy and a livenessProbe restart the pod.
Since the PR linked in my previous comment has landed in version 0.10.0 of the Helm operator, kubectl is no longer used in the Helm operator to request or list any resources (but it is still used to annotate resources from a release), and I expect this issue to be resolved.
If you do however run into the same (or new) symptoms, feel free to open up a new issue.
Describe the bug
The call to retrieve a list of namespaces here failed with a transient TLS error. The for loop bailed.
https://github.com/weaveworks/flux/blob/af9d3be07a240970cf1a935e4e88e0728052aad4/integrations/helm/status/status.go#L63
No further retry was made. The flux-helm-operator process didn't exit. http://127.0.0.1:3030/healthz continued to produce 200/OK
No further helm charts upgrades were started, despite updates to HelmChart resources.
To Reproduce
Steps to reproduce the behaviour:
flux-helm-operator
container on kuberneteskubectl -n flux port-forward pod/flux-helm-operator-588cb46cb8-sk9fw 3030
+curl -v http://127.0.0.1:3030/healthz
= 200/OKExpected behavior
I expected flux-helm-operator to retry connectivity to Kubernetes API endpoint, or to exit, or to report unhealthy and a livenessProbe restart the pod.
Logs
Additional context
Add any other context about the problem here, e.g
docker.io/weaveworks/flux:1.12.3
docker.io/weaveworks/helm-operator:0.9.1
v1.12.8
in AKSThe text was updated successfully, but these errors were encountered: