Controller for `Archive` CR?

[shajia-deshaw]

Changes to Archive CR are not reconciled by the side-car. Should we have a controller for it? cc: @Agalin

[Agalin]

I'm assuming you're talking about instanceSidecarConfiguration section, is that right? Everything else should be reloaded on each call (archive, backup, etc.).

That's a valid issue, recently I've noticed updating a plugin deployment doesn't bump sidecar images either. Both those things should be handled by the main plugin container but there are some things to consider - changing the image or resources requires a pod recreation and that should only happen automatically if cluster's configuration allows for that (in the future resources changes can be handled in-place but it's a pretty recent feature of k8s, only graduated to GA a few days ago with k8s 1.35).

While I believe we might be missing listeners on some events, in this case I'm not sure how it should be handled as the main CNPG operator doesn't watch other resources than the cluster. I'm not sure if we should somehow trigger an event in it (maybe by adding an archive config revision to the Cluster resource's plugin definition and touching it on Archive change?) or there is another way. Need to check CNPG-i and maybe the barman plugin.