Chore: Verify changes in the secrets are used by existing manifests

berops / claudie

Cloud-agnostic managed Kubernetes

https://docs.claudie.io/

Apache License 2.0

587 stars 40 forks source link

Chore: Verify changes in the secrets are used by existing manifests #1391

Open Despire opened 4 months ago

Despire commented 4 months ago

Description

After a cluster has been build, the secrets that have the credentials for various cloud providers could be updated with new ones. We need to ensure that the new workflow correctly handles changes to the secrets.

Exit criteria

[ ] Verify if claudie correctly handles changes to credentials with an existing cluster
[ ] Log any issue encountered under this Github issue

bernardhalas commented 4 months ago

Should we de-couple Secrets from the cluster state (current/desired)?