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

How to configure operator to use existing secret as the default cluster-wide secret for volume encryption? #654

Open
carpet-stain opened this issue Jun 15, 2022 · 0 comments

Comments

@carpet-stain
Copy link

We are deploying Portworx onto our Kubernetes cluster through the operator in a GitOps way through ArgoCD and we have successfully got this working.

The only caveat is that in each new environment we have to manually do:
kubectl exec $PORTWORX -c portworx -n kube-system -- /opt/pwx/bin/pxctl secrets set-cluster-key --secret

which, as of right now, is a manual process. We would like to see how we can configure the operator to consume an already existing secret for volume encryption so that we can fully automate deployments of Portworx across ephemeral environments.

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

No branches or pull requests

1 participant