Feature Approvers and Authors Please Read: Feature Promotion PR Testing

[Benjamin Elder]

Hello SIG Architecture, Kubernetes Contributors, please take a moment to review this update about feature promotion Pull Requests:

• There is now a comprehensive set of jobs triggered by any PR to `pkg/features/`.
• These jobs are not `Required` for merges currently, but I strongly advise checking any failures both as a PR Author and Approver when promoting feature gates.
• The jobs are:
  1. pull-kubernetes-e2e-kind-beta-enabled

  2. pull-kubernetes-e2e-kind-beta-features
  3. pull-kubernetes-e2e-kind-alpha-beta-enabled
  4. pull-kubernetes-e2e-kind-alpha-beta-features

  5. pull-kubernetes-e2e-kind-alpha-beta-enabled-conformance

• "enabled" means we turn on features and APIs, but run normal e2e tests.
• "conformance" means we run the conformance suite.

• "features" means we run e2e tests tagged for those features.

Keep in mind that tests tagged `WithFeatureGate` will also be promoted when the feature is promoted, and features that are enabled by default will generally be promoted to the default test suite.

Collectively these jobs should catch when enabling features breaks the cluster.

There are also release-blocking and release-informing versions of these jobs which do catch regressions but we'd prefer to catch them in presubmit when possible.

Thank you, and good luck with code freeze!
- Ben