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

Validate SLE Micro 5.5 in Rancher 2.9.0 - Imported Only #45868

Closed
daviswill2 opened this issue Jun 19, 2024 · 1 comment
Closed

Validate SLE Micro 5.5 in Rancher 2.9.0 - Imported Only #45868

daviswill2 opened this issue Jun 19, 2024 · 1 comment
Assignees
Labels
kind/enhancement Issues that improve or augment existing functionality priority/1 team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support
Milestone

Comments

@daviswill2
Copy link
Contributor

Request description:
Rancher Manager v2.9.0
Add support for SLE micro 5.5 imported only

@daviswill2 daviswill2 added the kind/bug Issues that are defects reported by users or that we know have reached a real release label Jun 19, 2024
@daviswill2 daviswill2 added this to the v2.9.0 milestone Jun 19, 2024
@daviswill2 daviswill2 removed the kind/bug Issues that are defects reported by users or that we know have reached a real release label Jun 19, 2024
@daviswill2 daviswill2 added priority/1 team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support enhancement kind/enhancement Issues that improve or augment existing functionality and removed enhancement labels Jun 19, 2024
@Josh-Diamond Josh-Diamond self-assigned this Jul 2, 2024
@Josh-Diamond
Copy link
Contributor

Ticket #45868 - Test Results -

Verified on Rancher v2.9.0-rc1 using SLE Micro 5.5 community ami-0bbae1f84573606ad:

Scenario Test Case Result
1. Import RKE2 w/ k8s 1.29.5+rke2r1
2. Import RKE2 w/ k8s 1.28.10+rke2r1 => upgrade to 1.29.5+rke2r1
3. Reboot RKE2 agent node
4. Import K3s w/ k8s 1.29.5+k3s1
5. Import K3s w/ k8s 1.28.10+k3s1 => upgrade to 1.29.5+k3s1
6. Reboot K3s agent node

Scenario 1 - ✅

  1. Spin up a standalone RKE2 w/ k8s v1.29.5+rke2r1
  2. Once active, import the cluster into Rancher
  3. Verified - cluster successfully imports
  4. Deploy downstream workloads and verify cluster functionality
  5. Verified - cluster active and functioning as expected

Scenario 2 - ✅

  1. Spin up a standalone RKE2 w/ k3s v1.28.10+rke2r1
  2. Once active, import the cluster into Rancher
  3. Verified - cluster successfully imports
  4. Upgrade the k8s version to v1.29.5+rke2r1 via Rancher UI
  5. Verified - cluster successfully upgrades
  6. Deploy downstream workloads and verify cluster functionality
  7. Verified - cluster and all pods active; as expected

Scenario 3 - ✅

  1. Reboot agent node of imported clusters from Scenario 1 and 2
  2. Verified - node reboots; cluster doesn't break; as expected

Scenario 4 - ✅

  1. Spin up a standalone K3s w/ k8s v1.29.5+k3s1
  2. Once active, import the cluster into Rancher
  3. Verified - cluster successfully imports
  4. Deploy downstream workloads and verify cluster functionality
  5. Verified - cluster active and functioning as expected

Scenario 5 - ✅

  1. Spin up a standalone K3s w/ k3s v1.28.10+k3s1
  2. Once active, import the cluster into Rancher
  3. Verified - cluster successfully imports
  4. Upgrade the k8s version to v1.29.5+k3s1 via Rancher UI
  5. Verified - cluster successfully upgrades
  6. Deploy downstream workloads and verify cluster functionality
  7. Verified - cluster and all pods active; as expected

Scenario 6 - ✅

  1. Reboot agent node of imported clusters from Scenario 4 and 5
  2. Verified - node reboots; cluster doesn't break; as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Issues that improve or augment existing functionality priority/1 team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support
Projects
None yet
Development

No branches or pull requests

3 participants