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

Encryption of block volumes using EncryptionClasses #3106

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nikolay-andreev
Copy link

What this PR does / why we need it:
Implement encryption of block volumes using EncryptionClass associated with PVC

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
GINKGO_FOCUS=encryption make test-e2e

  • Verify block volume is encrypted with a specific KeyID/Provider when PVC is associated with EncryptionClass.
  • Verify block volume is encrypted with the default KeyID/Provider when PVC is not associated with EncryptionClass but has encrypted StorageClass.
  • Verify block volume is recrypted the changing EncryptionClass associated with PVCs.
  • Verify block volume is recrypted when the EncryptionClass associated with PVCs has its key rotated.
  • Verify PVC creation fails when associated with EncryptionClass and StorageClass not supporting encryption.

SUCCESS! -- 5 Passed | 0 Failed | 0 Pending | 905 Skipped
PASS

Special notes for your reviewer:

Release note:
-->

Copy link

CLA Not Signed

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nikolay-andreev
Once this PR has been reviewed and has the lgtm label, please assign divyenpatel for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Nov 14, 2024
@k8s-ci-robot
Copy link
Contributor

Welcome @nikolay-andreev!

It looks like this is your first PR to kubernetes-sigs/vsphere-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/vsphere-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @nikolay-andreev. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 14, 2024
@divyenpatel
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 14, 2024
@k8s-ci-robot
Copy link
Contributor

@nikolay-andreev: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-vsphere-csi-driver-verify-golangci-lint 27acae3 link true /test pull-vsphere-csi-driver-verify-golangci-lint
pull-vsphere-csi-driver-verify-staticcheck 27acae3 link true /test pull-vsphere-csi-driver-verify-staticcheck

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@@ -431,6 +431,8 @@ const (
WorkloadDomainIsolationFSS = "workload-domain-isolation"
// VPCCapabilitySupervisor is a supervisor capability indicating if VPC FSS is enabled
VPCCapabilitySupervisor = "VPC_Supported"
// TODO: WCP_VMService_BYOK_FSS enables Bring Your Own Key (BYOK) capabilities.
BYOK_FSS = "byok"
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you confirm if this capability name exists in the required repository on GitLab.

@@ -358,6 +359,17 @@ func initSyncerComponents(ctx context.Context, clusterFlavor cnstypes.CnsCluster
os.Exit(0)
}
}()
if commonco.ContainerOrchestratorUtility.IsFSSEnabled(ctx, common.BYOK_FSS) &&
clusterFlavor == cnstypes.CnsClusterFlavorWorkload {
Copy link
Member

Choose a reason for hiding this comment

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

Can we move condition clusterFlavor == cnstypes.CnsClusterFlavorWorkload first, so FSS related log does not get printed for other flavors.


defer func() {
log.Info("Cleaning up vc sessions cns operator")
if r := recover(); r != nil {
Copy link
Member

Choose a reason for hiding this comment

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

if you are sharing the same VC session used by other services, we do not need to handle recover here to logout sessions. We are already doing this in the main - https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/cmd/syncer/main.go#L349-L354

@@ -22,7 +22,8 @@ require (
github.com/prometheus/client_golang v1.18.0
github.com/stretchr/testify v1.9.0
github.com/vmware-tanzu/vm-operator/api v1.8.2
github.com/vmware/govmomi v0.46.0
github.com/vmware-tanzu/vm-operator/external/byok v0.0.0-20241108223224-20f977201370
Copy link
Member

Choose a reason for hiding this comment

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

we need to make sure we have release tag for github.com/vmware-tanzu/vm-operator having this dependency. Do we have a plan to cut release for vm-operator for this change?

@@ -22,7 +22,8 @@ require (
github.com/prometheus/client_golang v1.18.0
github.com/stretchr/testify v1.9.0
github.com/vmware-tanzu/vm-operator/api v1.8.2
github.com/vmware/govmomi v0.46.0
github.com/vmware-tanzu/vm-operator/external/byok v0.0.0-20241108223224-20f977201370
github.com/vmware/govmomi v0.47.0-alpha.0.0.20241111085955-321b6f0907a4
Copy link
Member

Choose a reason for hiding this comment

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

we need to make sure to use govmomi release tag

Copy link
Contributor

Choose a reason for hiding this comment

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

Is that a repo rule? In VM Op we link to commits all the time. There is not always a release. It does not really matter from a technical standpoint as a tag is just a pointer to a ref. So I'm guessing it is a repo requirement?

Copy link
Member

Choose a reason for hiding this comment

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

at least before release we make sure we do not use any user commit from the repo.
this is repo specific requirement we are following.

Copy link
Member

Choose a reason for hiding this comment

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

we need to make sure to use govmomi release tag

Created a v0.46.1 release with just @nikolay-andreev 's changes and a small vcsim fix: vmware/govmomi@v0.46.0...v0.46.1

@@ -0,0 +1,247 @@
package crypto
Copy link
Member

Choose a reason for hiding this comment

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

we need to add Copyright header in new files.

)

type Provider interface {
DoesProfileSupportEncryption(ctx context.Context, profileID string) (bool, error)
Copy link
Member

Choose a reason for hiding this comment

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

add method docs

@@ -0,0 +1,294 @@
/*
Copyright 2021 The Kubernetes Authors.
Copy link
Member

Choose a reason for hiding this comment

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

2024

p.reinitialize = true
}

func (p *defaultProvider) getVcClient(ctx context.Context) (*cnsvsphere.VirtualCenter, error) {
Copy link
Member

Choose a reason for hiding this comment

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

lock sync.RWMutex
}

func (p *defaultProvider) DoesProfileSupportEncryption(ctx context.Context, profileID string) (bool, error) {
Copy link
Member

Choose a reason for hiding this comment

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

@@ -431,6 +431,8 @@ const (
WorkloadDomainIsolationFSS = "workload-domain-isolation"
// VPCCapabilitySupervisor is a supervisor capability indicating if VPC FSS is enabled
VPCCapabilitySupervisor = "VPC_Supported"
// TODO: WCP_VMService_BYOK_FSS enables Bring Your Own Key (BYOK) capabilities.
BYOK_FSS = "byok"
Copy link
Member

Choose a reason for hiding this comment

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

it is better to manage this with wcp capability so both vm service and csi can make use of common source of truth to determine if fss needs to be enabled or disabled.

@divyenpatel
Copy link
Member

@nikolay-andreev can you also fix linter issues on the PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants