You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found out the ReplicaSet is flagging a problem with the self signed certificate of the web hook:
Error creating: Internal error occurred: failed calling webhook "secrets-injector.1password.com": failed to call webhook: Post "https://secrets-injector.one-password.svc:443/inject?timeout=10s": x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "1password.com")
The inject has the following logs: http: TLS handshake error from 10.42.0.0:50982: remote error: tls: bad certificate
What did you expect to happen?
Pods to be scheduled, secrets to be injected
Steps to reproduce
On the latest K3s Kubernetes cluster
Deploy the helm chart (after fixing some bugs with it trying to be a hook 1Password/connect-helm-charts#150)
See the injector come online
Notice the logs mentioned above
Your environment
Secret Injector Version: 1.0.1
1Password CLI Version:
Connect Server Version: n/a
Kubernetes Version: v1.26.4+k3s1
What happened?
The inject has the following logs:
http: TLS handshake error from 10.42.0.0:50982: remote error: tls: bad certificate
What did you expect to happen?
Pods to be scheduled, secrets to be injected
Steps to reproduce
On the latest K3s Kubernetes cluster
Deploy the helm chart (after fixing some bugs with it trying to be a hook 1Password/connect-helm-charts#150)
See the injector come online
Notice the logs mentioned above
Notes & Logs
Used the following test deployment
The text was updated successfully, but these errors were encountered: