You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`KUBERNETES_VERSION`|`latest` - extract Kubernetes version from https://dl.k8s.io/ci/latest.txt (main's HEAD)<br>`latest-1.<MINOR>` - extract Kubernetes version from dl.k8s.io/ci/latest-1.<MINOR>.txt (release branch's HEAD) |
568
+
|`KUBERNETES_VERSION`|`latest` - extract Kubernetes version from https://dl.k8s.io/ci/latest.txt (main's HEAD)<br>`latest-1.<MINOR>` - extract Kubernetes version from dl.k8s.io/ci/latest-1.<MINOR>.txt (release branch's HEAD). For end-of-life minor versions, a static final patch release is returned instead (see `capz::util::get_eol_k8s_version` in `hack/util.sh`).|
569
569
|`WINDOWS_SERVER_VERSION`| Optional, can be `windows-2022` (default) or `windows-2025`|
570
570
|`KUBETEST_WINDOWS_CONFIG`| Default is `upstream-windows.yaml`. CAPZ contains various other configuration recipes in the `test/e2e/data/` directory; you may use any of those by referencing their file names as the value of `KUBETEST_WINDOWS_CONFIG` (e.g., `conformance-fast.yaml`), or you may drop in your own config files into `test/e2e/data/` and reference those. |
571
571
|`WINDOWS_CONTAINERD_URL`| Optional, can be any url to a `tar.gz` file containing binaries for containerd in the same format as upstream package |
@@ -595,7 +595,7 @@ You can optionally set the following variables:
595
595
|`AZURE_SSH_PUBLIC_KEY_FILE`| Use your own SSH key. |
596
596
|`SKIP_CLEANUP`| Skip deleting the cluster after the tests finish running. |
597
597
|`KUBECONFIG`| Provide your existing cluster kubeconfig filepath. If no kubeconfig is provided, `./kubeconfig` will be used. |
598
-
|`KUBERNETES_VERSION`| Desired Kubernetes version to test. You can pass in a definitive released version, e.g., "v1.24.0". If you want to use pre-released CI bits of a particular release you may use the "latest-" prefix, e.g., "latest-1.24"; you may use the very latest built CI bits from the kubernetes/kubernetes master branch by passing in "latest". If you provide a `KUBERNETES_VERSION` environment variable, you may not also use `CI_VERSION` (below). Use only one configuration variable to declare the version of Kubernetes to test. |
598
+
|`KUBERNETES_VERSION`| Desired Kubernetes version to test. You can pass in a definitive released version, e.g., "v1.24.0". If you want to use pre-released CI bits of a particular release you may use the "latest-" prefix, e.g., "latest-1.24"; you may use the very latest built CI bits from the kubernetes/kubernetes master branch by passing in "latest". For end-of-life Kubernetes versions whose CI artifacts are no longer published, CAPZ sets `KUBERNETES_VERSION` to a static final patch release instead (see `capz::util::get_eol_k8s_version` in `hack/util.sh`). If you provide a `KUBERNETES_VERSION` environment variable, you may not also use `CI_VERSION` (below). Use only one configuration variable to declare the version of Kubernetes to test. |
599
599
|`CI_VERSION`| Provide a custom CI version of Kubernetes (e.g., `v1.25.0-alpha.0.597+aa49dffc7f24dc`). If not specified, this will be determined from the KUBERNETES_VERSION above if it is an unreleased version. If you provide a `CI_VERSION` environment variable, you may not also use `KUBERNETES_VERSION` (above). |
600
600
|`TEST_CCM`| Build a cluster that uses custom versions of the Azure cloud-provider cloud-controller-manager and node-controller-manager images |
601
601
|`EXP_MACHINE_POOL`| Use [Machine Pool](../self-managed/machinepools.md) for worker machines. Defaults to true. |
0 commit comments