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.

Sign up for GitHub

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

Jump to bottom

[ClusterClass Operations] Cover k8s version update in E2E tests #643

Open
3 tasks
salasberryfin opened this issue Aug 6, 2024 · 0 comments
Open
3 tasks

[ClusterClass Operations] Cover k8s version update in E2E tests #643

salasberryfin opened this issue Aug 6, 2024 · 0 comments
Labels
area/clusterclass area/testing Indicates an issue related to test kind/feature

Comments

@salasberryfin
Copy link
Contributor

salasberryfin commented Aug 6, 2024 •
edited
Loading

This is issue is part of the epic #387.

Description

With the addition of the Kubernetes version upgrade feature (#640), it needs to be validated as part of the E2E. Ideally, we should validate that:

  • No Cluster can be used as target and conflict with other Kubernetes version spec.
  • One/multiple Cluster created with a Kubernetes version can be updated to a valid newer verison.
  • One/multiple Cluster created with a Kubernetes version should not be allowed to be updated to an invalid version (e.g. jumping minor versions).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/clusterclass area/testing Indicates an issue related to test kind/feature
Projects
CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Status: CAPI Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@salasberryfin