kubernetes/test/e2e
Tim Hockin 11a25bfeb6
De-share the Handler struct in core API (#105979)
* De-share the Handler struct in core API

An upcoming PR adds a handler that only applies on one of these paths.
Having fields that don't work seems bad.

This never should have been shared.  Lifecycle hooks are like a "write"
while probes are more like a "read". HTTPGet and TCPSocket don't really
make sense as lifecycle hooks (but I can't take that back). When we add
gRPC, it is EXPLICITLY a health check (defined by gRPC) not an arbitrary
RPC - so a probe makes sense but a hook does not.

In the future I can also see adding lifecycle hooks that don't make
sense as probes.  E.g. 'sleep' is a common lifecycle request. The only
option is `exec`, which requires having a sleep binary in your image.

* Run update scripts
2021-10-29 13:15:11 -07:00
..
apimachinery De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
apps De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
auth Fix CSR test to accept certs shorter than the requested duration 2021-10-01 09:14:54 -04:00
autoscaling retry PV create in e2e-test on API quota failure 2021-10-26 09:47:16 -04:00
chaosmonkey test: fix typo in chaosmonkey.go 2021-03-21 12:20:00 +09:00
cloud tag ginkgo tests affected by pdcsi migration for skipping and add storageclass check for statefulset and upgrade tests 2021-10-09 17:33:56 +00:00
common De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
framework De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
instrumentation test: e2e: HPA ContainerResource 2021-07-21 10:24:00 +05:30
kubectl De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
lifecycle fix ineffassign and varcheck 2021-07-14 08:41:22 -04:00
network De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
node De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
perftype hack/update-bazel.sh 2021-02-28 15:17:29 -08:00
reporters hack/update-bazel.sh 2021-02-28 15:17:29 -08:00
scheduling De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
storage De-share the Handler struct in core API (#105979) 2021-10-29 13:15:11 -07:00
testing-manifests updates pause image references 2021-08-29 21:50:05 -07:00
ui hack/update-bazel.sh 2021-02-28 15:17:29 -08:00
upgrades Changed code to improve output for files under test/e2e/upgrades/apps 2021-10-27 11:41:18 +05:30
windows [windows] Test: Check for failed sandbox pod when testing for RunAsUserName (#105943) 2021-10-28 14:04:59 -07:00
e2e-example-config.json Add viper support to core e2es 2016-09-15 18:38:01 -04:00
e2e.go initialize logging after flag parsing 2021-09-30 13:46:49 +02:00
e2e_test.go generated: remove usage of go-bindata 2021-06-29 19:16:48 +05:30
README.md test/e2e: Add ownership info to README 2021-03-17 16:48:11 -04:00
suites.go e2e: grab controller and scheduler metrics via port forwarding 2021-06-16 12:02:40 +02: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() {
    /* ... */
  })
  /* 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