Add e2e test for kubelet instance config #3126
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: HirazawaUi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/L
HirazawaUi
force-pushed
the
add-instance-config-tests
branch
from
0825734
to
2c7be5a
Compare
|
/retest |
HirazawaUi
force-pushed
the
add-instance-config-tests
branch
2 times, most recently
from
63cecf7
to
42dd92f
Compare
HirazawaUi
force-pushed
the
add-instance-config-tests
branch
from
42dd92f
to
7d1b378
Compare
|
/cc @neolit123 |
There was a problem hiding this comment.
i think we should do the following (when the FG is enabled):
- kubeadm init with "latest"
- kubeadm join with "latest"
- check that that instance config is on the nodes (it should be there)
- delete the instance config from the nodes
- kubeadm upgrade "latest" (it would be latest->latest technically)
- check if the instance config is on the nodes (it should be there)
| testgrid-dashboards: sig-cluster-lifecycle-kubeadm | ||
| testgrid-tab-name: kubeadm-kinder-instance-config-{{ dashVer .KubernetesVersion }} | ||
| testgrid-alert-email: sig-cluster-lifecycle-kubeadm-alerts@kubernetes.io | ||
| description: "OWNER: sig-cluster-lifecycle (kinder); Uses kubeadm/kinder to create a cluster using kubelet instance config and run kubeadm-e2e and the conformance suite" |
There was a problem hiding this comment.
i think we can skip the conformance suite, because it overlaps with other jobs.
| - --name={{ .vars.clusterName }} | ||
| - --loglevel=debug | ||
| timeout: 10m | ||
| - name: e2e |
There was a problem hiding this comment.
we can remove the conformance e2e task
Add e2e test for kubelet instance config.
relate: kubernetes/test-infra#33807