Skip to content

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

carlory
Copy link
Member

@carlory carlory commented Dec 11, 2024

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

  • feature.PodIndexLabel will be GA in 1.32.
  • feature.StatefulSet is a stable feature. It‘s safe to remove it because tests will be skipped if the cluster have no default sc.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added the release-note-none Denotes a PR that doesn't merit a release note. label Dec 11, 2024
@k8s-ci-robot
Copy link
Contributor

Please note that we're already in Test Freeze for the release-1.32 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.32.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Dec 11 00:11:49 UTC 2024.

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 11, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/test sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 11, 2024
@@ -446,7 +445,7 @@ done`}
*/
// TODO: once this test is stable, squash the functionality into pre-existing conformance test called "should create
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

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

@kannon92
Copy link
Contributor

I'd like confirmation that we have presubmits that are triggering these tests before merge.

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 12, 2024
@kannon92
Copy link
Contributor

IMO I would maybe considering moving these tests to conformance if they are not long running and don't require special environments.

@carlory
Copy link
Member Author

carlory commented Dec 13, 2024

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 [StatefulSet]. the job is ci-kubernetes-e2e-gci-gce-statefulset.

If the feature label StatefulSet were removed, the job ci-kubernetes-e2e-gci-gce-statefulset might be removed as well. the job ci-kubernetes-e2e-gci-gce-slow will be responsible for testing these clustered applications and report the results to the gce-slow dashboard for sig-apps. @kannon92

I'm not sure whether it is ok to promote PodIndexLabel e2e tests to Conformance at this time. The feature-gate isn't removed yet.

@carlory
Copy link
Member Author

carlory commented Dec 13, 2024

I'd like confirmation that we have presubmits that are triggering these tests before merge.我想确认我们有在合并之前触发这些测试的预提交。

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.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 15, 2025
@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jan 21, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: carlory
Once this PR has been reviewed and has the lgtm label, please assign kow3ns for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 21, 2025
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2025
@carlory
Copy link
Member Author

carlory commented Apr 21, 2025

/remove-lifecycle stale
/test pull-kubernetes-cmd

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2025
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 28, 2025
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 30, 2025
@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 30, 2025
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jun 30, 2025
@carlory
Copy link
Member Author

carlory commented Jun 30, 2025

/cc @kannon92

@k8s-ci-robot k8s-ci-robot requested a review from kannon92 June 30, 2025 06:45
@@ -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() {
Copy link
Member

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

@aojea
Copy link
Member

aojea commented Jun 30, 2025

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
Status: Needs Triage
Development

Successfully merging this pull request may close these issues.

5 participants