Change:
Related: Noticed this as part of Opened in response to: According to our , the e2e test is ineligible for Conformance. Specifically, the test in question is looking for guaranteed delivery of Events from specific sources (kubelet and default scheduler). This cannot be reasonably expected of all Kubernetes clusters, and thus the test should be demoted from Conformance. For historical context: It looks like this has been part of Conformance sometime since sometime prior to 2015-10-17 (we introduced the [Conformance] tag in 1.2, ref: We overhauled Conformance testing policy (including exclusion of Events) on 2018-10-08 (ref: ) If I wanted to be a language lawyer about this, I could say the policy covers ineligibility for promotion but said nothing about the existing corpus of tests. But I think this was just an honest oversight when we reviewed the existing Conformance tests. Due to the very nature of what this test is verifying, I don't think it's possible to rewrite to avoid Events. Thus, I think it should be demoted from Conformance. SIG Node is free to continue to treat this as release-blocking, but it's not something we can reasonably expect of any Kubernetes cluster /kind cleanup /priority important-soon /milestone v1.23 /sig architecture /area conformance because conformance /sig node because it's a sig-node test
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions 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
/assign Opened to address FYI Since y'all were commenting on
+1

Discussion:
visible at runtime in the container. release: v1.9 file: test/e2e/common/node/downwardapi.go <del> - testname: Pod events, verify event from Scheduler and Kubelet codename: '[sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running  [Conformance]' description: Create a Pod, make sure that the Pod can be queried. Create a event selector for the kind=Pod and the source is the Scheduler. List of the events MUST be at least one. Create a event selector for kind=Pod and the source is the Kubelet. List of the events MUST be at least one. Both Scheduler and Kubelet MUST send events when scheduling and running a Pod. release: v1.9 file: test/e2e/node/events.go </del> - testname: init-container-starts-app-restartalways-pod codename: '[sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartAlways pod [Conformance]'

var _ = SIGDescribe("Events", func() { f := framework.NewDefaultFramework("events") <del> /* Release: v1.9 Testname: Pod events, verify event from Scheduler and Kubelet Description: Create a Pod, make sure that the Pod can be queried. Create a event selector for the kind=Pod and the source is the Scheduler. List of the events MUST be at least one. Create a event selector for kind=Pod and the source is the Kubelet. List of the events MUST be at least one. Both Scheduler and Kubelet MUST send events when scheduling and running a Pod. */ framework.ConformanceIt("should be sent by kubelets and the scheduler about pods scheduling and running ", func() { </del> <ins> ginkgo.It("should be sent by kubelets and the scheduler about pods scheduling and running ", func() { </ins> podClient := f.ClientSet.CoreV1().Pods(f.Namespace.Name)