-
Notifications
You must be signed in to change notification settings - Fork 40.9k
e2e apps: remove unnecessary feature labels #129154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Dec 11 00:11:49 UTC 2024. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
@@ -446,7 +445,7 @@ done`} | |||
*/ | |||
// TODO: once this test is stable, squash the functionality into pre-existing conformance test called "should create |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @alaypatel07
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is GA in 1.32, so it should not be feature gated, if the test fails we have a problem
I'd like confirmation that we have presubmits that are triggering these tests before merge. /hold |
IMO I would maybe considering moving these tests to conformance if they are not long running and don't require special environments. |
According to the comments in these tests, it wouldn't be marked as Conformance because StatefulSet Conformance should not be dependent on specific applications. There is a dedicated job for testing these clustered applications which is labeled as If the feature label I'm not sure whether it is ok to promote |
https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/129154/pull-kubernetes-e2e-kind/1866694290139254784 shows that it triggered those tests which is related to PodIndexLabel. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: carlory The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Signed-off-by: carlory <[email protected]>
/cc @kannon92 |
@@ -1173,7 +1172,7 @@ var _ = SIGDescribe("StatefulSet", func() { | |||
}) | |||
}) | |||
|
|||
f.Describe("Deploy clustered applications", feature.StatefulSet, framework.WithSlow(), func() { | |||
f.Describe("Deploy clustered applications", framework.WithSlow(), func() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this depends on these manifests
zookeeperManifestPath = "test/e2e/testing-manifests/statefulset/zookeeper"
mysqlGaleraManifestPath = "test/e2e/testing-manifests/statefulset/mysql-galera"
redisManifestPath = "test/e2e/testing-manifests/statefulset/redis"
cockroachDBManifestPath = "test/e2e/testing-manifests/statefulset/cockroachdb"
I do not think we want to pull these things by default, so the feature tag seems a good guardrail here
test/e2e/testing-manifests/statefulset/redis/statefulset.yaml: image: registry.k8s.io/e2e-test-images/pets/redis-installer:1.5
test/e2e/testing-manifests/statefulset/redis/statefulset.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/redis/statefulset.yaml: image: debian:jessie
test/e2e/testing-manifests/statefulset/redis/statefulset.yaml: image: debian:jessie
test/e2e/testing-manifests/statefulset/etcd/statefulset.yaml: image: registry.k8s.io/etcd:3.2.24
test/e2e/testing-manifests/statefulset/etcd/statefulset.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/etcd/tester.yaml: image: registry.k8s.io/etcd-statefulset-e2e-test:0.0
test/e2e/testing-manifests/statefulset/etcd/tester.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/mysql-galera/statefulset.yaml: image: registry.k8s.io/galera-install:0.1
test/e2e/testing-manifests/statefulset/mysql-galera/statefulset.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/mysql-galera/statefulset.yaml: image: debian:jessie
test/e2e/testing-manifests/statefulset/mysql-galera/statefulset.yaml: image: registry.k8s.io/mysql-galera:e2e
test/e2e/testing-manifests/statefulset/mysql-upgrade/statefulset.yaml: image: mysql:5.7
test/e2e/testing-manifests/statefulset/mysql-upgrade/statefulset.yaml: image: gcr.io/google-samples/xtrabackup:1.0
test/e2e/testing-manifests/statefulset/mysql-upgrade/statefulset.yaml: image: mysql:5.7.15
test/e2e/testing-manifests/statefulset/mysql-upgrade/statefulset.yaml: image: gcr.io/google-samples/xtrabackup:1.0
test/e2e/testing-manifests/statefulset/mysql-upgrade/tester.yaml: image: registry.k8s.io/mysql-e2e-test:0.1
test/e2e/testing-manifests/statefulset/mysql-upgrade/tester.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/cassandra/statefulset.yaml: image: gcr.io/google-samples/cassandra:v13
test/e2e/testing-manifests/statefulset/cassandra/statefulset.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/cassandra/tester.yaml: image: registry.k8s.io/cassandra-e2e-test:0.1
test/e2e/testing-manifests/statefulset/cassandra/tester.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/cassandra/controller.yaml: image: gcr.io/google-samples/cassandra:v13
test/e2e/testing-manifests/statefulset/cockroachdb/statefulset.yaml: image: cockroachdb/cockroach-k8s-init:0.1
test/e2e/testing-manifests/statefulset/cockroachdb/statefulset.yaml: imagePullPolicy: IfNotPresent
test/e2e/testing-manifests/statefulset/cockroachdb/statefulset.yaml: image: cockroachdb/cockroach:v1.0
test/e2e/testing-manifests/statefulset/cockroachdb/statefulset.yaml: imagePullPolicy: IfNotPresent
test/e2e/testing-manifests/statefulset/zookeeper/statefulset.yaml: image: registry.k8s.io/e2e-test-images/pets/zookeeper-installer:1.5
test/e2e/testing-manifests/statefulset/zookeeper/statefulset.yaml: imagePullPolicy: Always
test/e2e/testing-manifests/statefulset/zookeeper/statefulset.yaml: image: java:openjdk-8-jr
@carlory commented, based on the comments I think that only the PodIndexLabel feature makes sense to remove, the statefuslet needs further analysis and discussion with the SIG owner, but I do not think we want to run arbitrary images by default on our tests |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: