Repository navigation
[release-4.22] CNTRLPLANE-4024: feat(azure): support managed HSM for KMS encryption #9437
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 8 commits into
openshift:release-4.22
from
hlipsig:cherry-pick-CNTRLPLANE-4025-to-release-4.22
Sep 3, 2026
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
76296fa
feat(api): add Azure Managed HSM support
hlipsig badc2db
chore(api): regenerate CRDs, clients, and vendor
hlipsig 40644fe
feat(cli): configure Azure KMS vault type from key URLs
hlipsig 1f2bdcf
feat(hypershift-operator): support Azure Managed HSM endpoints
hlipsig 402cac0
feat(control-plane-operator): configure KMS for Azure Managed HSM
hlipsig 2284e26
docs: document Azure Managed HSM support
hlipsig 4f7f8f7
chore(api): regenerate release 4.22 manifests
hlipsig ad40fdd
test(control-plane-operator): cover Managed HSM KMS configuration
hlipsig 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
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
Oops, something went wrong.
Oops, something went wrong.
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.
As a note, this rule is only enforceable if the parent field for this type - which appears to be optional - is not removed first.
If the parent field is removed, an end-user can re-apply a different configuration, circumventing this immutability constraint.
In order for true immutability, these types of rules need to be enforced at the highest parent field in the tree that is a required field.
I won't block on this as this has already merged previously, but we should at least make a note of needing to resolve this if we want true immutability here.