Skip to content
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

Add cluster-upgrade e2e tests #98

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Add cluster-upgrade e2e tests #98

merged 1 commit into from
Apr 11, 2024

Conversation

nasusoba
Copy link
Contributor

@nasusoba nasusoba commented Apr 11, 2024

  • Add two upgrade tests, one for single cp cluster, another for HA cluster
  • Modification for cluster-template.yaml
    • Decouple kind cluster image version and k3s version (as we do not have k8s binary on kind cluster image)
    • Remove k3s2 in the k3s version string, so that we could choose either k3s2 or k3s1
    • Add cluster.x-k8s.io/deployment-name: worker-md-0 selector as in the upgrade test, it relies on this selector for selecting machines (adding the selector will avoid selecting the controlplane machines)

Based on the local test result, it could upgrade a cluster from v1.28.6+k3s2 to v1.28.7+k3s1 by modifying KThreesControlPlane and MachineDeployment, so issue 84 might already be fixed.

add conditional build flag

give more time for machine upgrade

Signed-off-by: nasusoba <[email protected]>

fix test failure

Signed-off-by: nasusoba <[email protected]>
@mogliang mogliang merged commit 09c603f into k3s-io:main Apr 11, 2024
5 checks passed
@nasusoba nasusoba deleted the upgrade branch April 15, 2024 03:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants