Skip to content

PWX-26307: Use default gce account when device level account not prov…#105

Merged
pp511 merged 1 commit intolibopenstorage:masterfrom
pp511:PWX-26307-use-default-service-account-as-kms-account-when-device-level-account-info-not-specified
Aug 17, 2022
Merged

PWX-26307: Use default gce account when device level account not prov…#105
pp511 merged 1 commit intolibopenstorage:masterfrom
pp511:PWX-26307-use-default-service-account-as-kms-account-when-device-level-account-info-not-specified

Conversation

@pp511
Copy link
Copy Markdown
Contributor

@pp511 pp511 commented Aug 16, 2022

…ided for encryption

Signed-off-by: Priyanshu Pandey ppandey@purestorage.com

What this PR does / why we need it:

Which issue(s) this PR fixes (optional)
Closes #PWX-26307 [https://portworx.atlassian.net/browse/PWX-26307]

Special notes for your reviewer:
https://github.com/portworx/porx/pull/9762 has already been created to add support for disk encryption using customer managed key.

Customer should be able to provide Encrypt/Decrypt on their default gce account for disk encryption so that if device level kms account is not provided then

  1. if an account.json file has been updated in the pod via GOOGLE_APPLICATION_CREDENTIALS, that service account should be used as disk encryption kms account.
  2. If deployement is using instance gce account, that service account should be used as disk encryption kms account.

…ided for encryption

Signed-off-by: Priyanshu Pandey <ppandey@purestorage.com>
Copy link
Copy Markdown
Contributor

@adityadani adityadani left a comment

Choose a reason for hiding this comment

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

lgtm

@pp511 pp511 merged commit 07ce5dd into libopenstorage:master Aug 17, 2022
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