-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
testgrid/release: replace kubeadm-gce* jobs with kubeadm-kind(er)* #12493
Conversation
/approve |
LGTM label has been added. Git tree hash: ab44c043753c7c3b8e55eabae3e16ce2e1c72d98
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The kubeadm-gce* jobs are no longer supported due to the underlying deployer - kubernetes-anywhere. SIG Cluster Lifecycle spent a lot of effort this cycle implementing a solution for testing kubeadm upgrade and skew scenarios. This resulted in a tool called kinder, which is based on the kind backend but with a few more commands to support upgrade and skew. This PR does the following in release-x-all/informing dashboards: - replace kubeadm-gce-x with kubeadm-kind-x - replace kubeadm-gce-x-on-y with kubeadm-kinder-y-on-x - replace kubeadm-gce-upgrade-x-y with kubeadm-kinder-upgrade-x-y
/lgtm |
LGTM label has been added. Git tree hash: d3bf77b673585ed04db80416b932af4a0d7c3a97
|
The kubeadm-gce* jobs are no longer supported due to the
underlying deployer - kubernetes-anywhere being long deprecated.
SIG Cluster Lifecycle spent a lot of effort this cycle
implementing a solution for testing kubeadm upgrade and skew
scenarios.
This resulted in a tool kinder, which is based on the
kind backend but with a few more commands to support
upgrade and skew.
This PR does the following in release-x-all/informing dashboards:
*
*
y-on-xor (x+1)-on-(x)
is more correct, because we are creating ax
cluster using kubeadmx+1
./assign @spiffxp
cc @fabriziopandini @mariantalla @alejandrox1
/sig cluster-lifecycle
/sig release
/priority important-longterm
/kind cleanup
possibly we can close the following ticket using this PR:
fixes kubernetes/sig-release#518