-
Notifications
You must be signed in to change notification settings - Fork 113
Detect TLS cert secret changes in NodeSet reconciler #1990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
openshift-merge-bot
merged 1 commit into
openstack-k8s-operators:main
from
oliashish:fix/cert_change_detection_nodeset
Jul 23, 2026
+190
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -139,3 +139,36 @@ func ProcessAnsibleVarsFrom( | |
| } | ||
| return nil | ||
| } | ||
|
|
||
| // GetCertSecretHashes returns a map of secret-name to hash for all TLS cert | ||
| // secrets belonging to the given NodeSet. Cert secrets are identified by having | ||
| // both the NodeSetLabel and ServiceLabel labels set by EnsureTLSCerts. | ||
| func GetCertSecretHashes( | ||
| ctx context.Context, | ||
| helper *helper.Helper, | ||
| namespace string, | ||
| nodeSetName string, | ||
| ) (map[string]string, error) { | ||
| labelSelector := map[string]string{ | ||
| NodeSetLabel: nodeSetName, | ||
| } | ||
| secrets, err := secret.GetSecrets(ctx, helper, namespace, labelSelector) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't we have all secret names in the deployedSecretHashes? We can avoid this lus api call which is heavy. Also, we can reuses the label selector logic already in GetDeploymentHashesForService(). |
||
| if err != nil { | ||
| return nil, err | ||
| } | ||
|
|
||
| certHashes := make(map[string]string) | ||
| for i := range secrets.Items { | ||
| sec := &secrets.Items[i] | ||
| if _, hasSvcLabel := sec.Labels[ServiceLabel]; !hasSvcLabel { | ||
| continue | ||
| } | ||
| hash, err := secret.Hash(sec) | ||
| if err != nil { | ||
| helper.GetLogger().Error(err, "Unable to hash cert Secret", "secret", sec.Name) | ||
| return nil, err | ||
| } | ||
| certHashes[sec.Name] = hash | ||
| } | ||
| return certHashes, nil | ||
| } | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a review with claude has pointed out:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a new TLS service to the NodeSet means changing instance.Spec.Services. That changes instance.Spec, which changes ConfigHash which hashes the entire instance.Spec. Since ConfigHash != DeployedConfigHash, the deployment is already skipped before we reach here at
So the existing spec-hash check already covers this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also the case of changing a service (that is already in the NodeSet spec) to add a TLS cert, but that seems pretty unlikely.