Marko Mikulicic
Marko Mikulicic
bors try
bors help
This can mean many things; likely that the controller just doesn't start
Can you diff the yaml of the current release with the yaml produced by this PR?
I'm not working on this yet, feel free to take a stab
> Curious if this is still on your radar @mkmik ? Really looking for a resolution to #288. Or maybe https://github.com/bitnami-labs/sealed-secrets/blob/master/RELEASE-NOTES.md#allow-overwriting-existing-secrets (#331) means this is already covered? This issue is...
@yuha0 correct. These are two orthogonal issues that happen to be related in practice *if* your devops tooling happens to delete the managed secret when you cleanup your legacy secret...
We clearly need to fix this. Rebooting the controller is a hack. Sealed secrets controller needs to implement a proper controller loop that ensures the desired state matches the actual...
perhaps [controller-runtime](https://github.com/kubernetes-sigs/controller-runtime) could help with that. All controllers need to do the same things.