Skip to content

Add IsSecretHashInSync for scoped single-secret hash checking#700

Merged
stuggi merged 1 commit into
openstack-k8s-operators:mainfrom
lmiccini:add-IsSecretHashInSync
Jun 8, 2026
Merged

Add IsSecretHashInSync for scoped single-secret hash checking#700
stuggi merged 1 commit into
openstack-k8s-operators:mainfrom
lmiccini:add-IsSecretHashInSync

Conversation

@lmiccini

@lmiccini lmiccini commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

AreSecretHashesInSync checks all secrets across all NodeSets, which makes it unsuitable for controllers that need to track one specific secret without being affected by unrelated hash mismatches.

IsSecretHashInSync checks a single named secret against the secretHashes in all NodeSets. Returns inSync=true when the hash matches everywhere the secret is tracked, or when no NodeSet tracks it.

AreSecretHashesInSync checks all secrets across all NodeSets, which
makes it unsuitable for controllers that need to track one specific
secret without being affected by unrelated hash mismatches.

IsSecretHashInSync checks a single named secret against the
secretHashes in all NodeSets. Returns inSync=true when the hash
matches everywhere the secret is tracked, or when no NodeSet
tracks it.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

@stuggi stuggi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@stuggi stuggi merged commit ce00f67 into openstack-k8s-operators:main Jun 8, 2026
2 checks passed
@lmiccini lmiccini deleted the add-IsSecretHashInSync branch June 8, 2026 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants