-
Notifications
You must be signed in to change notification settings - Fork 268
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
Kuberhealthy OwnerRefInvalidNamespace Bug #903
Comments
It would be worth taking a look at the Kubernetes roadmap to see if cross-namespace checks are coming back in the future. For now, we probably have to drop owner references? |
Hi @joshulyne @integrii I am testing out k8s 1.20 upgrade in sandbox cluster and encountered exactly this. Was about to file a bug and saw this one :) |
It seems like we might need to quickly make a new build that drops owner references when the pod is being built in a different namespace. Unfortunately, it seems like owner references are not going to be supported by Kubernetes. I have raised this an existing issue in the kubernetes project (see reference above). |
@deads2k wrote the documentation on this one in the Kubernetes project and mentioned that in any future implementation, it needs to be "double opt-in" by both namespace owners somehow. |
Looks like we need to check if the checker pod is going into the same namespace as the kuberhealthy pod spawning it before adding the owner reference to it here |
We set ownerRef for all our khcheck pods to the kuberhealthy pod (since the kuberhealthy pod provisions/manages all these khcheck pods). However, for khchecks outside the kuberhealthy namespace (or whichever namespace kuberhealthy is running), we run into this
OwnerRefInvalidNamespace
error for kubernetes 1.20+ and the khcheck pods get automatically deleted:per k8s 1.20 release notes:
The text was updated successfully, but these errors were encountered: