Recording: https://www.youtube.com/watch?v=_sU62E6aHQk
Agenda:
- overview of test types
- walk through of code
show re-using kind clustermaybe in part2 :-)
Three types of e2e entry points:
-
CAPZ e2e
- these run on PRs
- typically uses Released kubernetes versions
- includes CAPI tests like
- rolling machinedelpoyments
- capi adoptions tests
- ./scripts/ci-e2e.sh
-
Conformance e2e
- optionally run on PRs
- run in periodic jobs in PROW
- uses CI build from the release specified:
- https://dl.k8s.io/ci/%s.txt
- latest
- latest-1.22
- https://dl.k8s.io/ci/%s.txt
- optionally build kubernetes binaries and use them for test (used for presubmits)
- ./scripts/ci-conformance.sh
-
Custom test suite entrypoint
- used by partner teams (cloud provider, azure disk/file csi)
- used to run any type of script after the cluster is up
- ./scripts/ci-entrypoint.sh
Always need to set these envs:
AZURE_CLIENT_ID,
AZURE_CLIENT_SECRET,
AZURE_SUBSCRIPTION_ID,
AZURE_TENANT_ID,
Some useful tools and commands
- kubie
- clusterctl
- kind get kubeconfig --name capz-e2e > kubeconfig.e2e
- https://www.jamessturtevant.com/posts/helpful-cluster-api-commands-for-developers/