-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
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
job/eg-gateway-helm-certgen #5223
Comments
please check the job/pod log. |
I see this issue with v1.3.0
To note I have only see this issue on some clusters I have applied v1.3.0 too Deployed using argocd as well |
cc @guydc |
Clean installation on a fresh cluster seems to work:
The logs from @owenhaynes seem to indicate some sort of authorization issue. The RBAC settings seem fine and are created in pre-install as well. Not sure why this is happening. @owenhaynes, @zhujiangtao123 - can you maybe provide more details on your setup? |
sorry, the problem is about my k8s |
@guydc I have a feeling its a argocd issue with all the hooks, maybe its worth adding the helm weights to the service account and roles so that they must be created before the job runs |
is this the same issue as #5082 ? cc @ryanhristovski @shahar-h |
helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.3.0 -n envoy-gateway-system --create-namespace
Pulled: docker.io/envoyproxy/gateway-helm:v1.3.0
Digest: sha256:9f142766a8388ebaa27d1afa9cc9ffb717d6a6fc96c6118d71642ba6522100dd
Error: INSTALLATION FAILED: failed pre-install: 1 error occurred:
* timed out waiting for the condition
job/eg-gateway-helm-certgen exec is failed
The text was updated successfully, but these errors were encountered: