Closed rchenzheng closed 3 years ago
Could you try with --set operator.create=true
?
Could you try with
--set operator.create=true
?
Thanks, looks like that did it. However, it'd be nice if it was documented or default to true
https://github.com/1Password/connect-helm-charts/tree/main/charts/connect https://support.1password.com/connect-deploy-kubernetes/#step-2-deploy-a-1password-connect-server
Your environment
Chart Version: connect-1.4.0
Helm Version: version.BuildInfo{Version:"v3.5.4", GitCommit:"1b5edb69df3d3a08df77c9902dc17af864ff05d1", GitTreeState:"dirty", GoVersion:"go1.16.3"}
Kubernetes Version: Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-21T01:11:42Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
What happened?
password connect does not create secrets although secret was created, the containers show no useful logs or errors
What did you expect to happen?
A kubernetes secrets should've been created automatically
Steps to reproduce
Notes & Logs
secrets
connect-api
connect-sync