-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.12: leadship election panics and crashes controller #4761
Comments
@alexec is this happening on your test? are you configuring |
@sarabala1979 no, it just seems to happen after about running for (maybe) 20m+ |
The issue is fixed in v1.20 Kubernetes. |
It is very hard to reproduce this issue. it is not consistent. I was able to reproduce 2 times in my local env with k3d. I got one more different error also after that I couldn't reproduce it.
|
FYI It looks like the fix is cherry-picked back to 1.18: kubernetes/kubernetes#80954 (comment) |
We've hit a similar issue around Here are logs, if that's helpful. If there's a way that we could have prevented this, would be great to know. And if anyone has a monitoring approach that would have alerted to something like this, I'd be v interested to learn. Thanks in advance:
This sequence repeats every five minutes when the workflow-container-controller starts. |
You need to set the |
Are you using env:
- name: LEADER_ELECTION_IDENTITY
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name |
I was using this 2.11.8, tagged with kustomize: I don't see any So either I made a mistake (very possible) or the error came from a 2.11.8 image. It resolved after upgrading to 2.12.2 — not sure whether that was the version upgrading or just a change in version. Wiping the whole Thanks you as ever for engaging and for the phenomenal library. |
It looks like someone (me?) has overwritten the v2.11.8 controller with a test version. |
Why oh why does Docker Hub allow you to overwrite images like this? It is impossible to prevent this from ever happening, even updating build scripts to check that a version does not exist, could not prevent this. |
@max-sixty Fixed.
|
Great — thanks a lot for tracking it down! |
K8s 1.19 client has a fix for this issue |
I'm pretty use we panic here and then we see other things shutting down.
kubernetes/client-go#754
The text was updated successfully, but these errors were encountered: