Dependent pods should restart when SealedSecret resources are modified.

[Stephen-ONeil]

Updated one of our SealedSecret-stored app config values, had to manually restart the app pod to get the new value in to its env vars. Not at all ideal, should be automatic, with rolling updates to avoid down time and all that nice-ness.

[Stephen-ONeil]

Update: or perhaps it would have if the secret was actually successfully synced, as the flux status notifications claimed

Closing till I gather more info, might be a different issue in the end.

[Stephen-ONeil]

Fixed the above update, unrelated bug, the application pod still required a restart in the end.

[vedantthapa]

I believe this is more of a kubernetes thing rather than a SealedSecret issue -

If a container already consumes a Secret in an environment variable, a Secret update will not be seen by the container unless it is restarted. There are third party solutions for triggering restarts when secrets change.

That is to say, it'd still exist when we migrate to SOPS unless we use a third-party solution like https://github.com/stakater/Reloader. However, that implies more pods.