Track source sercret for changes.

[zakkg3]

When using the source secret form another secret, we have to track for changes in the source and react to them.
for the use case at #35

[sa-ChristianAnton]

+1
would love to see this implemented. I am wanting to use ClusterSecret to replicate secrets created by operators, containing CA certs, credentials (crunchydata pgo, strimzi kafka) or others to other namespaces where the actual applications accessing these reside. The source secrets might at some point change, and ClusterSecrets taking care of updating the secret on "the other side" would be awesome!

[MarkCupitt]

Voting for this as well, we are using secrets generated by the Zalando PostgreSQL Operator, which is in its own namespace, however, consumers of the database services live ion other namespaces.

The Zalando operator implements automatic secret rotation, hence the need to monitor and propagate changes

We will also be looking at a Hashicorp Vault integration via the External Secrets Manager Operator, in this use case, the Vault will rotate the secret and we need it have it propagate via ClusterSecret if wee can

[MarkCupitt]

IN case anyone else is interested, we intend to also use ClusterSecret with https://github.com/stakater/Reloader to trigger pod and deployment restarts on secret rotations

[cedvan]

Hi, news to this feature ?

I want use Cluster Secret but I use Sealed Secret, and so without watch source secret is not possible 😢 .

I am not python developer to help sorry

[izzm]

IN case anyone else is interested, we intend to also use ClusterSecret with https://github.com/stakater/Reloader to trigger pod and deployment restarts on secret rotations

I tried do that way, but get a secret {sec_name} already exist in namesace message on restart and secret is not updated.

[zakkg3]

IN case anyone else is interested, we intend to also use ClusterSecret with https://github.com/stakater/Reloader to trigger pod and deployment restarts on secret rotations

I tried do that way, but get a secret {sec_name} already exist in namesace message on restart and secret is not updated.

this pr: #78 . introduces "REPLACE_EXISTING" var. When is set to true. all existing secrets will be replaced/updated.