Queue ReadinessProbe Kubelet Header e2e Test

[joshrider]

- e2e test verifies that readiness probe receives kube-probe header

Co-authored-by: Joshua Rider [email protected]

Supports #4649

Proposed Changes

• changes the /_healthz endpoint of the runtime test image to /healthz.
• changes /healthz path of runtime test image to return HTTP Status 400 if kubelet's User-Agent headers are not present
• adds an end-to-end test with a ReadinessProbe hitting runtime's /healthz path to verify the queue-proxy's addition of kubelet's User-Agent header

Release Note

NONE

[knative-prow-robot]

@joshrider: 0 warnings.

In response to this:

• e2e test verifies that readiness probe receives kube-probe header

Co-authored-by: Joshua Rider [email protected]

Supports #4649

Proposed Changes

• changes the /_healthz endpoint of the runtime test image to /healthz.
• changes /healthz path of runtime test image to return HTTP Status 400 if kubelet's User-Agent headers are not present
• adds an end-to-end test with a ReadinessProbe hitting runtime's /healthz path to verify the queue-proxy's addition of kubelet's User-Agent header

Release Note

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[shashwathi]

/assign @mattmoor

[mattmoor]

Just a nit about placement otherwise LGTM. thanks!

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[shashwathi]

@mattmoor : Moved the file to conformance package. Ready for another review 👍

[shashwathi]

/test pull-knative-serving-integration-tests

[mattmoor]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joshrider, mattmoor

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/OWNERS [mattmoor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.