Skip to content
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

[v2.9] Add support for Customer Managed Encryption Key #343

Merged
merged 1 commit into from
Feb 20, 2024

Conversation

mjura
Copy link
Contributor

@mjura mjura commented Feb 19, 2024

Add support for The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool.

For more information about protecting resources with Cloud KMS Keys please see:
https://cloud.google.com/compute/docs/disks/customer-managed-encryption

Issue: #261 (cherry picked from commit 53dede0)

What this PR does / why we need it:

Which issue(s) this PR fixes
Issue #

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests
  • backport needed

@mjura mjura requested a review from a team as a code owner February 19, 2024 07:27
Copy link
Contributor

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

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

Same comment as in main PR: #330 (review)

furkatgofurov7
furkatgofurov7 previously approved these changes Feb 19, 2024
Add support for The Customer Managed Encryption Key used to encrypt
the boot disk attached to each node in the node pool.

For more information about protecting resources with Cloud KMS Keys please see:
  https://cloud.google.com/compute/docs/disks/customer-managed-encryption

Issue: rancher#261
(cherry picked from commit 53dede0)
@mjura mjura merged commit 465adb3 into rancher:release-v2.9 Feb 20, 2024
7 checks passed
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.

3 participants