Skip to content

Remove unused simplyblock-pvc-keys secret from the dev chart - #458

Open
boddumanohar wants to merge 1 commit into
mainfrom
remove-pvc-keys-secret
Open

Remove unused simplyblock-pvc-keys secret from the dev chart#458
boddumanohar wants to merge 1 commit into
mainfrom
remove-pvc-keys-secret

Conversation

@boddumanohar

Copy link
Copy Markdown
Member

Summary

  • LVol encryption keys are now sourced entirely from KMS (internal or external); the CSI driver never handles key material and PVCs don't reference a Kubernetes secret for it (see csi-driver/docs/encrypted-volumes.md and sbcli's --crypto-key1/--crypto-key2 deprecation).
  • Drops the leftover simplyblock-pvc-keys Secret template and the csiSecret.simplybkPvc values from the development chart (helm-charts/charts/simplyblock-operator). The csi-driver's own vendored chart copy (csi-driver/charts/spdk-csi/latest/spdk-csi) had already dropped these.
  • No other references to this secret or crypto_key1/crypto_key2 exist in the operator, atlas-lib, or csi-driver Go code.

Test plan

  • helm template helm-charts/charts/simplyblock-operator --set externallyManagedSecret.create=true renders cleanly, no simplyblock-pvc-keys in output.
  • Repo-wide grep confirms no remaining references to simplyblock-pvc-keys, simplybkPvc, crypto_key1/crypto_key2.

🤖 Generated with Claude Code

LVol encryption keys are now sourced entirely from KMS (internal or
external), so the CSI driver never handles crypto_key1/crypto_key2 and
PVCs no longer reference a Kubernetes secret for them. The
simplyblock-pvc-keys secret template and its simplybkPvc values were
leftover from the pre-KMS flow; the csi-driver's own vendored chart
copy already dropped them.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.

1 participant