We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Chart Version: 1.15.0
Helm Version: v3.14.3
Kubernetes Version: 1.29
Fail:
{ "name": "1Password Connect API", "version": "1.7.2", "dependencies": [ { "service": "sqlite", "status": "ACTIVE", "message": "Connected to /home/opuser/.op/data/1password.sqlite" }, { "service": "account_data", "status": "NOT_SYNCED", "message": "Account data is not available because synchronization has not yet started" }, { "service": "sync", "status": "TOKEN_NEEDED" }, { "service": "1Password", "status": "UNINITIALIZED", "message": "Make a request with a valid bearer token to initialize" } ] }
With the second apply it runs through successful.
The first apply runs successfully.
Kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization helmCharts: - name: connect repo: https://1password.github.io/connect-helm-charts releaseName: onepassword-connect namespace: vault version: 1.15.0
Command:
kubectl kustomize . --enable-helm | kubectl apply -f -
After a while, it becomes successful on its own.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Your environment
Chart Version:
1.15.0
Helm Version:
v3.14.3
Kubernetes Version:
1.29
What happened?
Fail:
With the second apply it runs through successful.
What did you expect to happen?
The first apply runs successfully.
Steps to reproduce
Kustomization.yaml
Command:
Notes & Logs
After a while, it becomes successful on its own.
The text was updated successfully, but these errors were encountered: