-
Notifications
You must be signed in to change notification settings - Fork 337
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
chore(kuma-cp) change exec probes to http #1407
Conversation
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me!
envoy_names "github.com/kumahq/kuma/pkg/xds/envoy/names" | ||
) | ||
|
||
// OriginPrometheus is a marker to indicate by which ProxyGenerator resources were generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: the comment is about OriginPrometheus -> OriginAdmin
Shall we backport? |
…endpoints Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
}) | ||
} | ||
|
||
resources.Add(&core_xds.Resource{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this cluster if proxy.Dataplane.Spec.GetNetworking().Address == "127.0.0.1"
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, because we may still use it for Prometheus
Signed-off-by: Jakub Dyszkiewicz <[email protected]> (cherry picked from commit c1fa394)
Signed-off-by: Jakub Dyszkiewicz <[email protected]>
Summary
This PR changes the way we probe Kuma DP sidecar.
So far we were using exec healthchecks and
/ready
endpoint on Admin API. Admin API is exposed only on loopback interface for security reasons.This PR exposes
/ready
to the outside of the container, but only the/ready
endpoint. This way we can change probe from exec to httpReason
Containerd 1.4.0 had a bug of Pods being stuck at Terminating status when there was a container with exec probe.
awslabs/amazon-eks-ami#563