Closed SchoolGuy closed 1 year ago
Hi @SchoolGuy
Can you try to delete the RoleBinding pod-executor-namespaced
in your namespaces?
@Kidswiss Will do once I am home again from work.
It looks like the roleRef is immutable once it's set 🙈
I'm adding a point to the release notes once you can confirm the issue, so that people are aware that this might happen. Thanks for reporting.
I deleted the RoleBinding
and now the Jobs are starting again. As such the solution during an upgrade would be indeed to delete all RoleBinding
s and let them be recreated.
Thanks for confirming this!
I'm adding a note to the release and think of an automated solution for this problem.
Appendix: I double-checked and you need to either delete the k8up pod or restart it. The changes are not picked up dynamically. Sorry for not mentioning this earlier.
Since all Jobs get started at the same time again, this can potentially be a high-load scenario again.
I've opened a PR for helm hooks to cleanup stray resources: https://github.com/k8up-io/k8up/pull/863
Description
Either I am unlucky or I did the upgrade to 4.2.2 wrong but in either case, sadly my k8up is not working as expected atm.
Additional Context
So the
update
verb is present and as such I believe the upgrade to 2.7.1/4.2.2 should have worked as expected.Logs
That line is present for all Backups that are being created by my various schedules
Expected Behavior
k8up is not throwing errors.
Steps To Reproduce
Version of K8up
2.7.1 (app) / 4.2.2 (helmchart)
Version of Kubernetes
v1.26.4+k3s1
Distribution of Kubernetes
k3s