When deploying 1Password Connect, the connect pod fails to start because the SCC that is required (anyuid) isn't associated with the default Service Account. It is however associated with the onepassword-connect-operator Service Account.
By manually modifying the deployment, and specifying serviceAccount: onepassword-connect-operator, the issue is resolved and the deployment is successful.
What did you expect to happen?
The deployment to deploy successfully.
Steps to reproduce
Deploy the 1Password Connect Operator using Helm on OpenShift
Watch the 1Password Connect Deployment fail due to SCC errors
Notes & Logs
If you could add the following stanza to the connect definition in the Helm values, and use that to define the service account for the onepassword-connect Deployment, this issue will be resolve
Your environment
Chart Version: 1.15.0
Helm Version: N/A (deployed using ArgoCD)
Kubernetes Version: OpenShift 4.15.3
What happened?
When deploying 1Password Connect, the
connectpod fails to start because the SCC that is required (anyuid) isn't associated with thedefaultService Account. It is however associated with theonepassword-connect-operatorService Account. By manually modifying the deployment, and specifyingserviceAccount: onepassword-connect-operator, the issue is resolved and the deployment is successful.What did you expect to happen?
The deployment to deploy successfully.
Steps to reproduce
Notes & Logs
If you could add the following stanza to the
connectdefinition in the Helm values, and use that to define the service account for theonepassword-connectDeployment, this issue will be resolve