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

[TEST] v1.4.1 Release Test: Three node Harvester with Rancher #1767

Open
albinsun opened this issue Jan 8, 2025 · 1 comment
Open

[TEST] v1.4.1 Release Test: Three node Harvester with Rancher #1767

albinsun opened this issue Jan 8, 2025 · 1 comment
Assignees

Comments

@albinsun
Copy link
Contributor

albinsun commented Jan 8, 2025

Prerequisites

  1. VLAN 1 network on mgmt and 1 network on other NICs
  2. Create a new storage class apart from default one. Use the new storage class for some basic operations.
  3. 2 VMs with extra disk, data and computed md5sum- 1 running, 1 stopped
  4. 2 VM backup, snapshots - 1 backup when VM is running and 1 backup when VM is stooped

Test Steps

  1. Import Harvester in Rancher.
  2. Create RKE2 Harvester node driver cluster
    • Deploy cloud provider and csi driver all the clusters.
    • Necessary checks for cloud provider and csi driver working on cluster.
    • Scale down and scale up of clusters
    • Delete clusters.
  3. Create RKE2 Harvester node driver cluster (Terraform)
  4. Create RKE2 Harvester node driver cluster (Custom)
    • Deploy cloud provider and csi driver all the clusters.
    • Necessary checks for cloud provider and csi driver working on cluster.
    • Scale down and scale up of clusters
    • Delete clusters.
  5. Create RKE2 Harvester node driver cluster (Import)
    • Deploy cloud provider and csi driver all the clusters.
    • Necessary checks for cloud provider and csi driver working on cluster.
    • Scale down and scale up of clusters
    • Delete clusters.
  6. Upgrade Rancher.

Scenarios

Target Rancher and Guest K8s Version

  1. Rancher 2.10.1 + v1.31 (Manual)
  2. Rancher 2.9.5 + v1.30 (Manual)

Target Charts

  • harvester-cloud-provider -> v0.2.6
  • harvester-csi-driver -> v0.1.21

Reference

  1. [TEST] v1.4.0 Release Test: Three node Harvester with Rancher #1629
@albinsun albinsun self-assigned this Jan 8, 2025
@albinsun
Copy link
Contributor Author

albinsun commented Jan 17, 2025

R2.9.5 + K1.30 -> R2.10.1

Here we try operate all harvester operations via Rancher access

Prerequisites

  1. 🟢 Setup 3 nodes Harvester v1.4.1-rc1 cluster

    image

  2. 🟢 VLAN 1 network on mgmt and 1 network on other NICs

    image

  3. 🟢 Create a new storage class apart from default one. Use the new storage class for some basic operations.

    image

  4. 🟢 2 VMs with extra disk, data and computed md5sum- 1 running, 1 stopped

    image

  5. 🟢 2 VM backup, snapshots - 1 backup when VM is running and 1 backup when VM is stooped
    • backup-target
      image

    • backup
      image

    • snapshot
      image

Test Steps

  1. 🟢 Import Harvester in Rancher v2.9.5

    image

    image

  2. 🟢 Create Harvester IP Pool via Rancher

    image

  3. Create RKE2 v1.30 Harvester node driver cluster

    • 🟢 Create RKE2 cluster and upgrade cloud provider and csi driver
      • Cluster
        image
      • Apps
        image
    • 🟢 Necessary checks for cloud provider and csi driver working on cluster.
      • Deploy Nginx
        image
      • Create IPAM DHCP LoadBalancer
      • Create IPAM Pool LoadBalancer
        image
    • 🟢 Scale up cluster
      • Scale up
        image

      • Nginx deployment works
        image

      • DHCP LB works

      • Pool LB works
        image

    • 🟢 Scale down cluster
      • Scale down
        image

      • Nginx deployment works
        image

      • DHCP LB works

      • Pool LB works
        image

    • 🟡 Delete cluster

      image

      Hit known [BUG] kube-vip cloud-provider LB not released after cluster deletion harvester#1460

  4. Create RKE2 v1.30 Harvester node driver cluster (Custom)

    • 🟢 Create VMs for custom RKE2 nodes

      Ref. https://docs.harvesterhci.io/v1.4/rancher/cloud-provider/#deploying-to-the-rke2-custom-cluster-experimental
      ℹ️ After retrieving /etc/rancher/rke2/rke2.yaml. MUST replace server IP with the VIP address.

      image

    • 🟢 Create RKE2 cluster and upgrade cloud provider and csi driver
      • Cluster
        image
      • Apps
        image
    • 🟢 Necessary checks for cloud provider and csi driver working on cluster.
      • Deploy Nginx
        image
      • Create IPAM DHCP LoadBalancer
      • Create IPAM Pool LoadBalancer
        image
    • 🟢 Scale up cluster
      • Scale up (Create 1 more VM and do registration)
        image
        image

      • Nginx deployment works
        image

      • DHCP LB works

      • Pool LB works
        image

    • 🟢 Scale down cluster
      • Scale down (Delete the old one, thus also check pvc migration)

        • Before
          image
        • After (pvc migration take ~10 mins in QEMU/KVM env.)
          image
          image
      • Nginx deployment works
        image

      • DHCP LB works

      • Pool LB works
        image

    • 🟡 Delete cluster
      • Rancher
        image

      • Harvester (Need manually delete cuz we registered them)
        image

      Hit known [BUG] kube-vip cloud-provider LB not released after cluster deletion harvester#1460

  5. Create RKE2 v1.30 Harvester node driver cluster (Import)

  6. ⚪ Create RKE2 Harvester node driver cluster (Terraform)

    providers.tf.txt

    • Cluster

    • Upgrade cloud-provider and csi-driver

    • Deploy Nginx

    • DHCP LB works

    • Pool LB works

  7. ⚪ Upgrade Rancher to v2.8.9
    • RKE2 clsuter still works
  8. ⚪ Upgrade RKE2 version to v1.28
    • RKE2 clsuter still works
  9. ⚪ Scale up RKE2 cluster
    • RKE2 clsuter still works
  10. ⚪ Delete RKE2 Harvester node driver cluster (Terraform)

    providers.tf.txt

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

No branches or pull requests

1 participant