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
Unfortunately, the integration tests on k3d introduced in #492 (PR: #718) are unstable on our pipeline. I saw multiple failures because of the same reason:
• Installing capact Helm chart [started 11:42 UTC]
Error: All attempts fail:
✗ Installing capact Helm chart [took 4s]
#1: while installing Helm chart [capact]: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "[https://ingress-nginx-controller-admission.capact-system.svc:443/networking/v1beta1/ingresses?timeout=10s](https://ingress-nginx-controller-admission.capact-system.svc/networking/v1beta1/ingresses?timeout=10s)": dial tcp 10.43.112.55:443: connect: connection refused
#2: while installing Helm chart [capact]: failed to create resource: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "[https://ingress-nginx-controller-admission.capact-system.svc:443/networking/v1beta1/ingresses?timeout=10s](https://ingress-nginx-controller-admission.capact-system.svc/networking/v1beta1/ingresses?timeout=10s)": dial tcp 10.43.112.55:443: connect: connection refused
#3: while installing Helm chart [capact]: failed to create resource: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "[https://ingress-nginx-controller-admission.capact-system.svc:443/networking/v1beta1/ingresses?timeout=10s](https://ingress-nginx-controller-admission.capact-system.svc/networking/v1beta1/ingresses?timeout=10s)": dial tcp 10.43.112.55:443: connect: connection refused
Sometimes I needed to run the pipeline 4 times to make it successfully pass.
Description
Unfortunately, the integration tests on k3d introduced in #492 (PR: #718) are unstable on our pipeline. I saw multiple failures because of the same reason:
Sometimes I needed to run the pipeline 4 times to make it successfully pass.
See the sample runs:
It's worth noting that the PR and commit didn't introduce any changes related to any components run during these integration tests.
The text was updated successfully, but these errors were encountered: