kubernetes/test/e2e
Antonio Ojea 4482d1c2f4 e2e support Services with multiple EndpointSlices
A Service can use multiple EndpointSlices for its backend, when
using custom Endpoint Slices, the data plane should forward traffic
to any of the endpoints in the Endpointslices that belong to the
Service.

Change-Id: I80b42522bf6ab443050697a29b94d8245943526f
2023-03-07 13:00:46 +00:00
..
apimachinery Merge pull request #115987 from yuanchen8911/cleanup 2023-02-28 01:47:29 -08:00
apps Merge pull request #113270 from rrangith/fix/create-pvc-for-pending-pod 2023-03-03 10:24:58 -08:00
architecture e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
auth e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
autoscaling Reduce possible number of scale steps to improve test stability 2023-02-24 13:19:05 +00:00
chaosmonkey e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
cloud e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
common test: fix ginkgolinter issues 2023-02-22 19:36:05 +01:00
dra DRA: fix CDI spec version 2023-03-05 16:49:56 +02:00
framework Remove AWS legacy cloud provider + EBS in-tree storage plugin 2023-03-06 14:01:15 +00:00
instrumentation e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
kubectl test: fix ginkgolinter issues 2023-02-22 19:36:05 +01:00
lifecycle e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
network e2e support Services with multiple EndpointSlices 2023-03-07 13:00:46 +00:00
node retry on conflict for negative TerminationGracePeriodSeconds update 2023-03-01 12:55:58 +08:00
perftype hack/update-bazel.sh 2021-02-28 15:17:29 -08:00
reporters e2e: comment the known limitation of the ProgressReporter 2022-12-23 18:43:49 +08:00
scheduling Graduate PodSchedulingReadiness to beta 2023-02-17 18:45:20 -08:00
storage Remove AWS legacy cloud provider + EBS in-tree storage plugin 2023-03-06 14:01:15 +00:00
testing-manifests Merge pull request #115107 from swatisehgal/handle-device-mgr-recovery-sample-dp-changes 2023-03-02 05:42:55 -08:00
upgrades e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
windows Merge pull request #116189 from marosset/windows-hyperv-basic-e2e-test 2023-03-01 22:27:07 -08:00
e2e_test.go Merge pull request #114417 from chendave/ginkgo_fix_spec 2023-01-12 03:28:56 -08:00
e2e-example-config.json
e2e.go Merge pull request #115678 from pohly/e2e-full-reports 2023-02-10 15:07:29 -08:00
README.md e2e: accept context from Ginkgo 2022-12-10 19:50:18 +01:00
suites.go e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00

test/e2e

This is home to e2e tests used for presubmit, periodic, and postsubmit jobs.

Some of these jobs are merge-blocking, some are release-blocking.

e2e test ownership

All e2e tests must adhere to the following policies:

  • the test must be owned by one and only one SIG
  • the test must live in/underneath a sig-owned package matching pattern: test/e2e/[{subpath}/]{sig}/..., e.g.
    • test/e2e/auth - all tests owned by sig-auth
    • test/e2e/common/storage - all tests common to cluster-level and node-level e2e tests, owned by sig-node
    • test/e2e/upgrade/apps - all tests used in upgrade testing, owned by sig-apps
  • each sig-owned package should have an OWNERS file defining relevant approvers and labels for the owning sig, e.g.
# test/e2e/node/OWNERS
# See the OWNERS docs at https://go.k8s.io/owners

approvers:
- alice
- bob
- cynthia
emeritus_approvers:
- dave
reviewers:
- sig-node-reviewers
labels:
- sig/node
  • packages that use {subpath} should have an imports.go file importing sig-owned packages (for ginkgo's benefit), e.g.
// test/e2e/common/imports.go
package common

import (
	// ensure these packages are scanned by ginkgo for e2e tests
	_ "k8s.io/kubernetes/test/e2e/common/network"
	_ "k8s.io/kubernetes/test/e2e/common/node"
	_ "k8s.io/kubernetes/test/e2e/common/storage"
)
  • test ownership must be declared via a top-level SIGDescribe call defined in the sig-owned package, e.g.
// test/e2e/lifecycle/framework.go
package lifecycle

import "github.com/onsi/ginkgo"

// SIGDescribe annotates the test with the SIG label.
func SIGDescribe(text string, body func()) bool {
	return ginkgo.Describe("[sig-cluster-lifecycle] "+text, body)
}
// test/e2e/lifecycle/bootstrap/bootstrap_signer.go

package bootstrap

import (
	"github.com/onsi/ginkgo"
	"k8s.io/kubernetes/test/e2e/lifecycle"
)
var _ = lifecycle.SIGDescribe("[Feature:BootstrapTokens]", func() {
  /* ... */
  ginkgo.It("should sign the new added bootstrap tokens", func(ctx context.Context) {
    /* ... */
  })
  /* etc */
})

These polices are enforced:

  • via the merge-blocking presubmit job pull-kubernetes-verify
  • which ends up running hack/verify-e2e-test-ownership.sh
  • which can also be run via make verify WHAT=e2e-test-ownership

more info

See kubernetes/community/.../e2e-tests.md