-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
use exec probe for queue proxy readiness check #4148
Changes from all commits
8f6cbea
fd34450
bf6cd5e
fdeb347
1828a41
75df793
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,10 +20,6 @@ import ( | |
"math" | ||
"strconv" | ||
|
||
"k8s.io/apimachinery/pkg/api/resource" | ||
|
||
"k8s.io/apimachinery/pkg/util/intstr" | ||
|
||
"github.com/knative/pkg/logging" | ||
pkgmetrics "github.com/knative/pkg/metrics" | ||
"github.com/knative/pkg/system" | ||
|
@@ -33,8 +29,8 @@ import ( | |
"github.com/knative/serving/pkg/autoscaler" | ||
"github.com/knative/serving/pkg/deployment" | ||
"github.com/knative/serving/pkg/metrics" | ||
"github.com/knative/serving/pkg/queue" | ||
corev1 "k8s.io/api/core/v1" | ||
"k8s.io/apimachinery/pkg/api/resource" | ||
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | ||
) | ||
|
||
|
@@ -63,9 +59,8 @@ var ( | |
|
||
queueReadinessProbe = &corev1.Probe{ | ||
Handler: corev1.Handler{ | ||
HTTPGet: &corev1.HTTPGetAction{ | ||
Port: intstr.FromInt(networking.QueueAdminPort), | ||
Path: queue.RequestQueueHealthPath, | ||
Exec: &corev1.ExecAction{ | ||
Command: []string{"/ko-app/queue", "-probe", "true"}, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you confirm that it's our ultimate goal to:
This seems like a reasonable first step, but I wanted to confirm we have a shared understanding of the end state. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
}, | ||
}, | ||
// We want to mark the service as not ready as soon as the | ||
|
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.
Should we make this a flag so it can be kept consistent with TimeoutSeconds in the probe configuration? Maybe we shouldn't do this until we pass the entire probe descriptor through?
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.
Yeah, the idea was that this was separate from the issue of passing in the full probe to have something user-defined applied via the queue-proxy. There are a bunch of things in this file that will change once we start passing all of the configuration in.