Change:
other platforms like Windows. release: v1.9 file: test/e2e/common/network/networking.go <ins> - testname: Proxy, validate Proxy responses codename: '[sig-network] Proxy version v1 A set of valid responses are returned for both pod and service Proxy [Conformance]' description: Attempt to create a pod and a service. A set of pod and service endpoints MUST be accessed via Proxy using a list of http methods. A valid response MUST be returned for each endpoint. release: v1.24 file: test/e2e/network/proxy.go </ins> - testname: Proxy, validate ProxyWithPath responses codename: '[sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance]'

Discussion:
needs to be resolved before a number of e2e tests can be completed. 23 Oct 2021 [x] two weeks soak end date : 5 Nov 2021 [x] test promotion pr : kubernetes/kubernetes According to this APIsnoop query, there are still some remaining PodProxyOptions endpoints which are untested. As the these endpoints are redirected to their related endpoints. Create pod and confirm that the pod is running so that the tested endpoints can be found. Create a http.Client that checks for a redirect so that status code can be checked Loop through all http verbs, testing that the pod proxy endpoint returns the required 301 status code. Discover useragents: List endpoints hit by the test: Display endpoint coverage change: If a test with these calls gets merged, test coverage will go up by 7 points This test is also created with the goal of conformance promotion. After the merger of the test was updated to cover both the Pod and Service Proxy endpoint. Therefore If a test with these calls gets merged, test coverage will go up by 12 points connectCoreV1DeleteNamespacedPodProxy connectCoreV1DeleteNamespacedServiceProxy connectCoreV1OptionsNamespacedPodProxy connectCoreV1OptionsNamespacedServiceProxy connectCoreV1PatchNamespacedPodProxy connectCoreV1PatchNamespacedServiceProxy connectCoreV1PostNamespacedPodProxy connectCoreV1PostNamespacedServiceProxy connectCoreV1PutNamespacedPodProxy connectCoreV1PutNamespacedServiceProxy connectCoreV1HeadNamespacedPodProxy onnectCoreV1HeadNamespacedServiceProxy /sig testing /sig architecture /area conformance
/assign
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale To be revisited in 1.21
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at .

/lifecycle stale
/remove-lifecycle stale Focus for 1.22
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
/remove-lifecycle stale Focus for 1.23
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale Focus for 1.23 Will move forward once merged
/open Waiting for 2 week flake free before promotion
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted