Remove Pod Scheduling from harvester rke2 and rke1

  • Related issues: #2642 [BUG] Remove Pod Scheduling from harvester rke2 and rke1

Category:

  • Rancher

Test Information

Test Environment: 1 node harvester on local kvm machine Harvester version: v1.0-44fb5f1a-head (08/10) Rancher version: v2.6.7-rc7

Environment Setup

  1. Prepare Harvester master node
  2. Prepare Rancher v2.6.7-rc7
  3. Import Harvester to Rancher
  4. Set ui-offline-preferred: Remote
  5. Go to Harvester Support page
  6. Download Kubeconfig
  7. Copy the content of Kubeconfig

Verification Steps

RKE2 Verification Steps

  1. Open Harvester Host page then edit host config
  2. Add the following key value in the labels page:
    • topology.kubernetes.io/zone: zone_bp
    • topology.kubernetes.io/region: region_bp image
  3. Open the RKE2 provisioning page
  4. Expand the show advanced
  5. Click add Node selector in Node scheduling
  6. Use default Required priority
  7. Click Add Rule
  8. Provide the following key/value pairs
  9. topology.kubernetes.io/zone: zone_bp
  10. topology.kubernetes.io/region: region_bp
  11. Provide the following user data 
    password: 123456
chpasswd: { expire: False }
ssh_pwauth: True
  12. Create the RKE2 guest cluster
  13. Go to Harvester Virtual Machine page
  14. Edit yaml of the RKE2 guest cluster image
  15. Check the node affinity label have written into the yaml image
  16. Check the guest cluster VM have no error message image
  17. Check can provision RKE2 cluster correctly image

RKE1 Verification Steps

  1. Follow the steps 1 ~ 7 of the RKE2 verification section
  2. Go to Rancher Cluster Management page, add the RKE1 node template
  3. Click add Node selector in Node scheduling
  4. Use default Required priority
  5. Click Add Rule
  6. Provide the following key/value pairs
    • topology.kubernetes.io/zone: zone_bp
    • topology.kubernetes.io/region: region_bp image
  7. Create the RKE1 guest cluster
  8. Go to Harvester Virtual Machine page
  9. Edit yaml of the RKE1 guest cluster
  10. Check the node affinity label have written into the yaml image
  11. Check the guest cluster VM have no error message image
  12. Check can provision RKE1 cluster without error image

Expected Results

  • Pod Scheduling did not appear on the RKE1 template provisioning advanced options image

  • Pod Scheduling did not appear on the RKE2 provisioning advanced options image

  • Can deploy guest RKE1 cluster vm to specific Harvester node matching the Node scheduling image image

  • Can deploy guest RKE2 cluster vm to specific Harvester node matching the Node scheduling image image

  • Can deploy guest RKE1 cluster vm to specific Harvester node matching the Node scheduling with external kubconfig

  • Can deploy guest RKE2 cluster vm to specific Harvester node matching the Node scheduling with external kubconfig