-
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
Injector is skipping Contour and Envoy pods #3910
Comments
So after removing contour and envoy from: func HasExistingSidecars(podSpec *corev1.PodSpec) bool {
for _, container := range podSpec.Containers {
if strings.HasPrefix(container.Image, "gcr.io/linkerd-io/proxy:") ||
strings.HasPrefix(container.Image, "gcr.io/istio-release/proxyv2:") ||
strings.HasPrefix(container.Image, "docker.io/envoyproxy/envoy-alpine:") ||
container.Name == k8s.ProxyContainerName ||
container.Name == "istio-proxy" {
return true
}
}
for _, ic := range podSpec.InitContainers {
if strings.HasPrefix(ic.Image, "gcr.io/linkerd-io/proxy-init:") ||
strings.HasPrefix(ic.Image, "gcr.io/istio-release/proxy_init:") ||
ic.Name == "linkerd-init" ||
ic.Name == "istio-init" {
return true
}
}
return false
} The linkerd-proxy from the envoy pod crashes at startup with:
|
@stefanprodan |
The better solution is to add a proper service account to envoy. I submitted a PR to remove the envoy/contour restrictions. |
Bug Report
What is the issue?
Contour 1.1.0 comes with header mutation support so I tried to run it inside linkerd but the injector skips both contour and envoy pods.
How can it be reproduced?
Logs, error output, etc
linkerd check
outputEnvironment
Possible solution
Additional context
The text was updated successfully, but these errors were encountered: