Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
No k8s secret created. How to troubleshoot?
Hello. Excited to get this working.
one connect pods are green. I've created my CRD for a OnePasswordItem. I've applied it. I see the CRD in the Object Explorer on GKE. However, my actual k8s secr...
Thank you for clarifying that! I think I know what the issue could be.
The magic that automatically creates Kubernetes secrets is not included in the base setup of Connect. That requires running a separate operator that talks with the Kubernetes API.
Fortunately, that is all https://github.com/1Password/connect-helm-charts/tree/main/charts/connect#deploying-1password-connect-kubernetes-operator. So enabling it should be as simple as running the following Helm command:
helm upgrade connect 1password/connect --reuse-values --set operator.create=true
The operator requires a Connect token (with read access to all vaults that it should create secrets for) to communicate with Connect. That can be stored in a k8s secret, like this:
kubectl create secret generic onepassword-token--from-literal=token=INSERT_TOKEN_HERE
If all goes well, you should end up with an extra onepassword-connect-operator deployment.
Let me know if that helps.
Joris
