-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Viz crashes Pods created by ingress controller #12344
Comments
@qts0312 This is bizarre for sure. Can we see the full Pod manifests you're working with here? I can't really think of any reason that this should be happening. |
Here are Pod manifests in this case. Are you referring to this? $ kubectl get pods -n default
NAME READY STATUS RESTARTS AGE
contour-gw-0-687fb5c7ff-jptq5 1/2 CrashLoopBackOff 4 (12s ago) 2m11s
contour-gw-0-687fb5c7ff-ntgj2 1/2 CrashLoopBackOff 4 (6s ago) 2m11s
envoy-gw-0-8lrmm 2/3 Running 0 2m11s
envoy-gw-0-l5r52 2/3 Running 0 2m11s
ratings-v1 2/2 Running 0 2m12s
ratings-v2 2/2 Running 0 2m12s
$ kubectl get pods -n projectcontour
NAME READY STATUS RESTARTS AGE
contour-gateway-provisioner-5fd5647b95-hz2v6 1/1 Running 0 5m59s |
@qts0312 Yes, can we get the YAML for the two Contour Pods? |
These Pods are created by Contour to implement the gateway functionality automatically, so I don't have the exact YAML for them. |
You can get it with e.g. |
What is the issue?
I am using Linkerd as service mesh and Contour as ingress controller in my cluster. After I install viz, Pods created by ingress controller turn into
CrashLoopBackOff
status.How can it be reproduced?
As the configuration below, my ingress controller deploys several Pods to complete gateway function. However, after I install viz, I apply this configuration but Pods created by ingress controller crash while they work well before the installation of viz.
Logs, error output, etc
Log of Pod created by ingress controller.
Before installing viz
After installing viz
output of
linkerd check -o short
Environment
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: