You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SIG testing: alpha/beta "enabled" and "conformance" presubmits
We've had kind-alpha-beta-features and kind-beta-features jobs for a while. The
original purpose was to run stable tests in a cluster with features enabled to
detect when enabling those breaks stable functionality. Later the jobs were
extended to also run all tests which should work in such a cluster. The
kind-alpha-features job got removed recently because it's not necessarily a
valid cluster configuration.
What this adds for the both cluster configs is:
- "-enabled": running only tests for on-by-default features, i.e. excluding tests for
stable features. This matches the original purpose of the jobs.
- "-enabled-conformance": restricts the test selection even further to only
conformance tests.
Both can eventually get promoted to release informing or even blocking.
Only presubmits get added for now. If testing the jobs in a trial PR works, the
corresponding periodics can be added.
# we need privileged mode in order to do docker in docker
307
+
securityContext:
308
+
privileged: true
309
+
resources:
310
+
limits:
311
+
cpu: 7
312
+
memory: 9000Mi
313
+
requests:
314
+
cpu: 7
315
+
memory: 9000Mi
316
+
317
+
- name: pull-kubernetes-e2e-kind-beta-enabled
318
+
cluster: k8s-infra-prow-build
319
+
annotations:
320
+
description: Runs tests with no special requirements in a KinD cluster where beta feature gates and APIs are enabled, i.e. this does not include tests for off-by-default beta features.
description: Runs tests with no special requirements in a KinD cluster where alpha and beta feature gates and APIs are enabled, i.e. this does not include tests for alpha features and off-by-default beta features.
0 commit comments