diff --git a/src/css/custom.css b/src/css/custom.css index 83edc11c..e7fe76b8 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -188,4 +188,12 @@ a.btn.navbar__github::before { .openapi-left-panel__container{ border-right: 0px !important; -} \ No newline at end of file +} +/* Hide items with hide-sidebar-item class (used to hide Upgrade section) */ +.menu__list-item.hide-sidebar-item { display: none !important; } + +/* Hide Troubleshooting > Rancher doc entry explicitly */ +.menu__list-item a.menu__link[href*="/troubleshooting/rancher"] { + display: none !important; +} + diff --git a/static/img/v1.2/advanced-hv/create-image-with-nfs-csi.png b/static/img/v1.2/advanced-hv/create-image-with-nfs-csi.png new file mode 100644 index 00000000..914cf4be Binary files /dev/null and b/static/img/v1.2/advanced-hv/create-image-with-nfs-csi.png differ diff --git a/static/img/v1.2/advanced-hv/create-policy-with-all-nodes.png b/static/img/v1.2/advanced-hv/create-policy-with-all-nodes.png new file mode 100644 index 00000000..325a5336 Binary files /dev/null and b/static/img/v1.2/advanced-hv/create-policy-with-all-nodes.png differ diff --git a/static/img/v1.2/advanced-hv/create-policy-with-specific-node.png b/static/img/v1.2/advanced-hv/create-policy-with-specific-node.png new file mode 100644 index 00000000..f7b662fc Binary files /dev/null and b/static/img/v1.2/advanced-hv/create-policy-with-specific-node.png differ diff --git a/static/img/v1.2/advanced-hv/csi-driver-config-external.png b/static/img/v1.2/advanced-hv/csi-driver-config-external.png new file mode 100644 index 00000000..9fb7357a Binary files /dev/null and b/static/img/v1.2/advanced-hv/csi-driver-config-external.png differ diff --git a/static/img/v1.2/advanced-hv/customsuseimages.md b/static/img/v1.2/advanced-hv/customsuseimages.md deleted file mode 100644 index 0451982a..00000000 --- a/static/img/v1.2/advanced-hv/customsuseimages.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -id: customsuseimages -sidebar_position: 8 -sidebar_label: Custom SUSE VM Images -title: "Custom SUSE VM Images" -keywords: -- Custom Images -Description: How to create custom SLES and openSUSE guest virtual machine images -draft: true ---- - - - - - -SUSE provides [SUSE Linux Enterprise (SLE)](https://www.suse.com/download/sles/) and [openSUSE Leap](https://get.opensuse.org/leap/) virtual machine (VM) images suitable for use in Harvester. These images are built on the [openSUSE Build Service](https://build.opensuse.org/) (OBS) using the [Kiwi](https://osinside.github.io/kiwi/) image building tool, and can be used immediately after downloading. - -For most cases, you can use the *Minimal VM Cloud* qcow2 images because these include the cloud-init tool necessary for automatic VM configuration. Other image variants require you to log onto the VM console and then perform initial configuration. - -:::info -The *Minimal VM Cloud* images were named *Minimal VM OpenStack Cloud* in releases earlier than SLES 15 SP5 and openSUSE 15.5. -::: - -## Using the openSUSE Build Service (OBS) - -You can create custom images based on what SUSE provides using OBS [image templates](https://build.opensuse.org/image_templates), which are pre-configured Kiwi image configurations. For example, if you want use other packages with SLE 15 SP5, you can create an image using the *SLE 15 SP5 Minimal* template. OBS provides an interface for adding packages and automatically builds the image, which you can download and then upload to Harvester. For more information, see the [OBS User Guide](https://openbuildservice.org/help/manuals/obs-user-guide/). - -### 1. Create a custom image based on an existing template. - -1. Go to https://build.opensuse.org/image_templates. You must sign in to your openSUSE account to access the resources. - -1. Select the template that you want to use. - -1. Specify a name for the image, and then select **Create appliance**. - - ![](/img/v1.3/advanced/custom-vm-01-select-template.png) - - OBS automatically builds the image. By default, the interface shows the **Overview** tab, which contains information such as the number of included packages and the build status. - - ![](/img/v1.3/advanced/custom-vm-02-image-overview.png) - -### 2. Select image profiles and add packages. - -1. Go to the **Software** tab. - -1. Select the image profiles that you want OBS to build. - - :::info - For most cases, you can use the *Minimal VM Cloud* qcow2 images because these include the cloud-init tool necessary for automatic VM configuration. Other image variants require you to log onto the VM console and then perform initial configuration. - ::: - - ![](/img/v1.3/advanced/custom-vm-03-image-software.png) - -1. (Optional) Add and remove packages. - - ![](/img/v1.3/advanced/custom-vm-04-image-software-packages.png) - - ![](/img/v1.3/advanced/custom-vm-05-image-software-add-package.png) - -### 3. (Optional) Switch to *View Package* mode. - -*View Package* mode provides more granular control over configuration. To switch, click the *View Package* icon in the navigation bar. - -![](/img/v1.3/advanced/custom-vm-06-view-package.png) - -The **Source Files** section of the **Overview** tab shows all the files that comprise your Kiwi template. You can edit any of the files by selecting the corresponding file name. - -![](/img/v1.3/advanced/custom-vm-07-view-package-details.png) - -### 4. (Optional) Edit the configuration file `Minimal.kiwi`. - -Select the file name to open the text editor. The `` section lists the packages to be installed. You can specify additional packages for each image profile. - -By default, the *Cloud* image profile (``) installs the *kernel-default-base* package. In the following example, that package is replaced with *kernel-default*, which includes modules necessary for iSCSI support. - -![](/img/v1.3/advanced/custom-vm-08-edit-kiwi-config.png) - -### 5. Wait for OBS to finish building the image. - -Once the process is completed, the **Build Results** section on the **Overview** tab shows the status *succeeded*. - -![](/img/v1.3/advanced/custom-vm-09-build-succeeded.png) - -The **Build Results** section also contains a download link for the new image. - -![](/img/v1.3/advanced/custom-vm-10-binaries-link.png) - -![](/img/v1.3/advanced/custom-vm-11-binaries-download.png) - -### 6. Enable publishing to share the image. - -To allow the public to download your custom image, go to the **Repositories** tab of your OBS project and enable the *Publish* flag. - -![](/img/v1.3/advanced/custom-vm-12-project-publish-repositories.png) - -Your image is published to https://download.opensuse.org/ (under `repositories/home:/YOUR_USER_NAME:/branches:/SUSE:/Templates:/Images:/`). - -![](/img/v1.3/advanced/custom-vm-13-download.openuse.org.png) - -## Using the Kiwi Command-line Tool - -As an alternative to the openSUSE Build Service, you can create images locally using the Kiwi command-line tool. For more information about the tool, see [Building Linux System Appliances with KIWI Next Generation (KIWI NG)](https://documentation.suse.com/appliance/kiwi-9/html/kiwi/index.html). - -To create custom images, you must first download the file `Minimal.kiwi`, and the scripts `config.sh` and `editbootinstall_rpi.sh` from the corresponding project on OBS. - -| OS | openSUSE Build Service Project | -| -------------------|-----------------------------------------------------------------------------------| -| SLE 15 SP5 | https://build.opensuse.org/package/show/SUSE:SLE-15-SP5:GA/kiwi-templates-Minimal | -| openSUSE Leap 15.5 | https://build.opensuse.org/package/show/openSUSE:Leap:15.5/kiwi-templates-Minimal | -| SLE 15 SP4 | https://build.opensuse.org/package/show/SUSE:SLE-15-SP4:GA/kiwi-templates-Minimal | -| openSUSE Leap 15.4 | https://build.opensuse.org/package/show/openSUSE:Leap:15.4/kiwi-templates-Minimal | diff --git a/static/img/v1.2/advanced-hv/kubeovn-operator.png b/static/img/v1.2/advanced-hv/kubeovn-operator.png new file mode 100644 index 00000000..cfe3dfcb Binary files /dev/null and b/static/img/v1.2/advanced-hv/kubeovn-operator.png differ diff --git a/static/img/v1.2/advanced-hv/new-storageclass-rep-2.png b/static/img/v1.2/advanced-hv/new-storageclass-rep-2.png new file mode 100644 index 00000000..ee9fea52 Binary files /dev/null and b/static/img/v1.2/advanced-hv/new-storageclass-rep-2.png differ diff --git a/static/img/v1.2/advanced-hv/no-uplink.png b/static/img/v1.2/advanced-hv/no-uplink.png new file mode 100644 index 00000000..83e7c139 Binary files /dev/null and b/static/img/v1.2/advanced-hv/no-uplink.png differ diff --git a/static/img/v1.2/advanced-hv/nvidia-driver-toolkit.png b/static/img/v1.2/advanced-hv/nvidia-driver-toolkit.png new file mode 100644 index 00000000..ebf03100 Binary files /dev/null and b/static/img/v1.2/advanced-hv/nvidia-driver-toolkit.png differ diff --git a/static/img/v1.2/advanced-hv/set-to-default-sc copy.png b/static/img/v1.2/advanced-hv/set-to-default-sc copy.png new file mode 100644 index 00000000..6d1881f9 Binary files /dev/null and b/static/img/v1.2/advanced-hv/set-to-default-sc copy.png differ diff --git a/static/img/v1.2/advanced-hv/set-to-default-sc.png b/static/img/v1.2/advanced-hv/set-to-default-sc.png new file mode 100644 index 00000000..6d1881f9 Binary files /dev/null and b/static/img/v1.2/advanced-hv/set-to-default-sc.png differ diff --git a/static/img/v1.2/rancher-hv/harvester-container-dashboard.png b/static/img/v1.2/rancher-hv/harvester-container-dashboard.png new file mode 100644 index 00000000..129ac357 Binary files /dev/null and b/static/img/v1.2/rancher-hv/harvester-container-dashboard.png differ diff --git a/static/img/v1.2/vm-import-controller-hv/EnableAddon copy.png b/static/img/v1.2/vm-import-controller-hv/EnableAddon copy.png new file mode 100644 index 00000000..e1df4839 Binary files /dev/null and b/static/img/v1.2/vm-import-controller-hv/EnableAddon copy.png differ diff --git a/static/img/v1.3/troubleshooting-hv/edit-rancher-monitoring-yaml.png b/static/img/v1.3/troubleshooting-hv/edit-rancher-monitoring-yaml.png new file mode 100644 index 00000000..899cf11c Binary files /dev/null and b/static/img/v1.3/troubleshooting-hv/edit-rancher-monitoring-yaml.png differ diff --git a/static/img/v1.3/troubleshooting-hv/edit-rancher-monitoring.png b/static/img/v1.3/troubleshooting-hv/edit-rancher-monitoring.png new file mode 100644 index 00000000..81f91e88 Binary files /dev/null and b/static/img/v1.3/troubleshooting-hv/edit-rancher-monitoring.png differ diff --git a/static/img/v1.4/storagenetwork-hv/storage-network-disabled.png b/static/img/v1.4/storagenetwork-hv/storage-network-disabled.png new file mode 100644 index 00000000..e12e5158 Binary files /dev/null and b/static/img/v1.4/storagenetwork-hv/storage-network-disabled.png differ diff --git a/static/img/v1.4/storagenetwork-hv/storage-network-enabled.png b/static/img/v1.4/storagenetwork-hv/storage-network-enabled.png new file mode 100644 index 00000000..23c57aa4 Binary files /dev/null and b/static/img/v1.4/storagenetwork-hv/storage-network-enabled.png differ diff --git a/static/img/v1.4/storagenetwork-hv/storagenetwork-diff.png b/static/img/v1.4/storagenetwork-hv/storagenetwork-diff.png new file mode 100644 index 00000000..2178fa2d Binary files /dev/null and b/static/img/v1.4/storagenetwork-hv/storagenetwork-diff.png differ diff --git a/static/img/v1.4/storagenetwork-hv/storagenetwork-same.png b/static/img/v1.4/storagenetwork-hv/storagenetwork-same.png new file mode 100644 index 00000000..7021eb75 Binary files /dev/null and b/static/img/v1.4/storagenetwork-hv/storagenetwork-same.png differ diff --git a/static/img/v1.6/vm-migration-network-hv/vm-migration-network-enabled.png b/static/img/v1.6/vm-migration-network-hv/vm-migration-network-enabled.png new file mode 100644 index 00000000..135cb08c Binary files /dev/null and b/static/img/v1.6/vm-migration-network-hv/vm-migration-network-enabled.png differ diff --git a/versioned_docs/version-v1.6/advanced/addons/kubeovn-operator.md b/versioned_docs/version-v1.6/advanced/addons/kubeovn-operator.md index 6c42f662..810928d2 100644 --- a/versioned_docs/version-v1.6/advanced/addons/kubeovn-operator.md +++ b/versioned_docs/version-v1.6/advanced/addons/kubeovn-operator.md @@ -10,19 +10,19 @@ title: "Kube-OVN Operator" _Available as of v1.6.0_ -[`kubeovn-operator`](https://github.com/harvester/kubeovn-operator) is used to manage the lifecycle of [Kube-OVN](https://github.com/kubeovn/kube-ovn) as a secondary CNI on underlying Harvester clusters. +[`kubeovn-operator`](https://github.com/harvester/kubeovn-operator) is used to manage the lifecycle of [Kube-OVN](https://github.com/kubeovn/kube-ovn) as a secondary CNI on underlying Hypervisor clusters. ## Enabling `kubeovn-operator` -You must enable `kubeovn-operator` to deploy Kube-OVN to a Harvester cluster for advanced SDN capabilities such as virtual private cloud (VPC) and subnets for virtual machine workloads. +You must enable `kubeovn-operator` to deploy Kube-OVN to a Hypervisor cluster for advanced SDN capabilities such as virtual private cloud (VPC) and subnets for virtual machine workloads. -1. On the Harvester UI, go to **Advanced** > **Add-ons**. +1. On the Hypervisor UI, go to **Advanced** > **Add-ons**. 1. Select **kubeovn-operator (Experimental)**, and then select **⋮** > **Enable**. - ![](/img/kubeovn-operator.png) + ![](/img/v1.2/advanced-hv/kubeovn-operator.png) -The add-on deploys `kubeovn-operator` and creates the default `Configuration` object named `configuration.kubeovn.io`, which uses sane Harvester-specific defaults for configuring the Kube-OVN CNI. +The add-on deploys `kubeovn-operator` and creates the default `Configuration` object named `configuration.kubeovn.io`, which uses sane Hypervisor-specific defaults for configuring the Kube-OVN CNI. The following is an example of a `Configuration` object: @@ -181,13 +181,13 @@ spec: :::info important -Ensure that the Kube-OVN IPv4 pod and service CIDR blocks do not overlap with the Harvester pod and service CIDR blocks. +Ensure that the Kube-OVN IPv4 pod and service CIDR blocks do not overlap with the Hypervisor pod and service CIDR blocks. ::: :::caution -This `Configuration` object has been validated against Harvester installations. You can fine-tune the object by editing the `kubeovn-operator` add-on YAML, but exercise caution when making changes to the `configurationSpec` field. +This `Configuration` object has been validated against Hypervisor installations. You can fine-tune the object by editing the `kubeovn-operator` add-on YAML, but exercise caution when making changes to the `configurationSpec` field. ::: @@ -250,4 +250,4 @@ done You must reboot each node to complete the uninstallation process. -Once the nodes are rebooted, you can disable the `kubeovn-operator` add-on from the Harvester UI. +Once the nodes are rebooted, you can disable the `kubeovn-operator` add-on from the Hypervisor UI. diff --git a/versioned_docs/version-v1.6/advanced/addons/lvm-local-storage.md b/versioned_docs/version-v1.6/advanced/addons/lvm-local-storage.md index 27131064..b19f3427 100644 --- a/versioned_docs/version-v1.6/advanced/addons/lvm-local-storage.md +++ b/versioned_docs/version-v1.6/advanced/addons/lvm-local-storage.md @@ -10,17 +10,17 @@ title: "Local Storage Support (Experimental)" :::note -**harvester-csi-driver-lvm** is an *experimental* add-on. It is not included in the Harvester ISO, but you can download it from the [experimental-addons repository](https://github.com/harvester/experimental-addons). For more information about experimental features, see [Feature Labels](../../getting-started/document-conventions.md#feature-labels). +**harvester-csi-driver-lvm** is an *experimental* add-on. It is not included in the Hypervisor ISO, but you can download it from the [experimental-addons repository](https://github.com/harvester/experimental-addons). For more information about experimental features, see [Feature Labels](../../getting-started/document-conventions.md#feature-labels). ::: -Harvester allows you to use local storage on the host to create persistent volumes for your workloads with better performance and latency. This functionality is made possible by LVM, which provides logical volume management facilities on Linux. +Hypervisor allows you to use local storage on the host to create persistent volumes for your workloads with better performance and latency. This functionality is made possible by LVM, which provides logical volume management facilities on Linux. The **harvester-csi-driver-lvm** add-on is a CSI driver that supports local path provisioning through LVM. ## Installing and Enabling the Add-on -If you are using the Harvester kubeconfig file, you can install the add-on by performing the following steps: +If you are using the Hypervisor kubeconfig file, you can install the add-on by performing the following steps: 1. Install the add-on by running the following command: @@ -28,7 +28,7 @@ If you are using the Harvester kubeconfig file, you can install the add-on by pe # kubectl apply -f https://raw.githubusercontent.com/harvester/experimental-addons/main/harvester-csi-driver-lvm/harvester-csi-driver-lvm.yaml ``` -1. On the Harvester UI, go to **Advanced** > **Add-ons**. +1. On the Hypervisor UI, go to **Advanced** > **Add-ons**. 1. Select **harvester-csi-driver-lvm (Experimental)**, and then select **⋮** > **Enable**. @@ -40,13 +40,13 @@ A volume group combines physical volumes to create a single storage structure th :::note -Harvester currently does not allow you to modify the volume group composition (add or remove disks) after you create a logical volume. This issue will be addressed in a future release. +Hypervisor currently does not allow you to modify the volume group composition (add or remove disks) after you create a logical volume. This issue will be addressed in a future release. ::: 1. Verify that the **harvester-csi-driver-lvm** add-on is installed. -1. On the Harvester UI, go to the **Hosts** screen. +1. On the Hypervisor UI, go to the **Hosts** screen. 1. Select the target host, and then select **⋮** > **Edit Config**. @@ -80,7 +80,7 @@ You can only use one type of local volume in each volume group. If necessary, cr ::: -1. On the Harvester UI, go to the **Storage** screen. +1. On the Hypervisor UI, go to the **Storage** screen. 1. Create a new StorageClass and select **LVM** in the **Provisioner** list. @@ -96,7 +96,7 @@ You can only use one type of local volume in each volume group. If necessary, cr ![](/img/v1.4/csi-driver-lvm/create-lvm-sc-03.png) - - **Volume Group Type**: Select the type of local volume that matches your requirements. Harvester currently supports **striped** and **dm-thin**. + - **Volume Group Type**: Select the type of local volume that matches your requirements. Hypervisor currently supports **striped** and **dm-thin**. ![](/img/v1.4/csi-driver-lvm/create-lvm-sc-04.png) @@ -110,7 +110,7 @@ For more information, see [StorageClass](../storageclass.md). ## Creating a Volume with LVM -1. On the Harvester UI, go to the **Volumes** screen. +1. On the Hypervisor UI, go to the **Volumes** screen. 1. Create a new volume using the LVM StorageClass that you created. @@ -118,7 +118,7 @@ For more information, see [StorageClass](../storageclass.md). :::note - The status **Not Ready** is normal because Harvester creates the LVM volume only when the first workload is created. + The status **Not Ready** is normal because Hypervisor creates the LVM volume only when the first workload is created. ::: @@ -146,7 +146,7 @@ You can also create a new virtual machine with the volume of the LVM StorageClas ## Creating Snapshots for an LVM Volume -1. On the Harvester UI, go to the **Settings** screen. +1. On the Hypervisor UI, go to the **Settings** screen. 1. In the **csi-driver-config** section, select **⋮** > **Edit Setting**. diff --git a/versioned_docs/version-v1.6/advanced/addons/managed-dhcp.md b/versioned_docs/version-v1.6/advanced/addons/managed-dhcp.md index d103a7d4..fd1112a4 100644 --- a/versioned_docs/version-v1.6/advanced/addons/managed-dhcp.md +++ b/versioned_docs/version-v1.6/advanced/addons/managed-dhcp.md @@ -10,15 +10,15 @@ title: "Managed DHCP (Experimental)" :::note -**harvester-vm-dhcp-controller** is an *experimental* add-on. It is not included in the Harvester ISO, but you can download it from the [experimental-addons repository](https://github.com/harvester/experimental-addons). For more information about experimental features, see [Feature Labels](../../getting-started/document-conventions.md#feature-labels). +**harvester-vm-dhcp-controller** is an *experimental* add-on. It is not included in the Hypervisor ISO, but you can download it from the [experimental-addons repository](https://github.com/harvester/experimental-addons). For more information about experimental features, see [Feature Labels](../../getting-started/document-conventions.md#feature-labels). ::: -You can configure IP pool information and serve IP addresses to VMs running on Harvester clusters using the embedded Managed DHCP feature. This feature, which is an alternative to the standalone DHCP server, leverages the [harvester-vm-dhcp-controller](https://github.com/harvester/vm-dhcp-controller) add-on to simplify guest cluster deployment. +You can configure IP pool information and serve IP addresses to VMs running on Hypervisor clusters using the embedded Managed DHCP feature. This feature, which is an alternative to the standalone DHCP server, leverages the [harvester-vm-dhcp-controller](https://github.com/harvester/vm-dhcp-controller) add-on to simplify guest cluster deployment. :::note -Harvester uses the planned infrastructure network so you must ensure that network connectivity is available and plan the IP pools in advance. +Hypervisor uses the planned infrastructure network so you must ensure that network connectivity is available and plan the IP pools in advance. ::: @@ -72,13 +72,13 @@ kubectl -n kube-system get pods -l component=kube-apiserver -o yaml | grep "serv ::: -After installation, enable the add-on on the **Dashboard** screen of the Harvester UI or using the command-line tool kubectl. +After installation, enable the add-on on the **Dashboard** screen of the Hypervisor UI or using the command-line tool kubectl. ![](/img/v1.3/vm-dhcp-controller/enable-addon.png) ## Using the Add-on -1. On the **Dashboard** screen of the Harvester UI, [create a VM Network](../../networking/harvester-network.md#create-a-vm-network). +1. On the **Dashboard** screen of the Hypervisor UI, [create a VM Network](../../networking/harvester-network.md#create-a-vm-network). ![](/img/v1.3/vm-dhcp-controller/vm-network.png) @@ -233,7 +233,7 @@ The add-on introduces the following new CRDs: The IPPool CRD allows you to define IP pool information. You must map each IPPool object to a specific NetworkAttachmentDefinition (NAD) object, which must be created beforehand. :::note -Multiple CRDs named "IPPool" are used in the Harvester ecosystem, including a similarly-named CRD in the `loadbalancer.harvesterhci.io` API group. To avoid issues, ensure that you are working with the **IPPool CRD in the `network.harvesterhci.io` API group**. For more information about IPPool CRD operations in relation to load balancers, see [IP Pool](../../networking/ippool.md). +Multiple CRDs named "IPPool" are used in the Hypervisor ecosystem, including a similarly-named CRD in the `loadbalancer.harvesterhci.io` API group. To avoid issues, ensure that you are working with the **IPPool CRD in the `network.harvesterhci.io` API group**. For more information about IPPool CRD operations in relation to load balancers, see [IP Pool](../../networking/ippool.md). ::: Example: diff --git a/versioned_docs/version-v1.6/advanced/addons/nvidiadrivertoolkit.md b/versioned_docs/version-v1.6/advanced/addons/nvidiadrivertoolkit.md index 3dca348d..a49ca7e6 100644 --- a/versioned_docs/version-v1.6/advanced/addons/nvidiadrivertoolkit.md +++ b/versioned_docs/version-v1.6/advanced/addons/nvidiadrivertoolkit.md @@ -10,18 +10,18 @@ title: "NVIDIA Driver Toolkit" _Available as of v1.3.0_ -nvidia-driver-toolkit is an add-on that allows you to deploy out-of-band NVIDIA GRID KVM drivers to your existing Harvester clusters. +nvidia-driver-toolkit is an add-on that allows you to deploy out-of-band NVIDIA GRID KVM drivers to your existing Hypervisor clusters. :::note -The toolkit only includes the correct Harvester OS image, build utilities, and kernel headers that allow NVIDIA drivers to be compiled and loaded from the container. You must download the NVIDIA KVM drivers using a valid NVIDIA subscription. For guidance on identifying the correct driver for your NVIDIA GPU, see the [NVIDIA documentation](https://www.nvidia.com/en-au/drivers/vgpu-software-driver/). +The toolkit only includes the correct Hypervisor OS image, build utilities, and kernel headers that allow NVIDIA drivers to be compiled and loaded from the container. You must download the NVIDIA KVM drivers using a valid NVIDIA subscription. For guidance on identifying the correct driver for your NVIDIA GPU, see the [NVIDIA documentation](https://www.nvidia.com/en-au/drivers/vgpu-software-driver/). ::: -The Harvester ISO does not include the nvidia-driver-toolkit container image. Because of its size, the image is pulled from Docker Hub by default. If you have an air-gapped environment, you can download and push the image to your private registry. The **Image Repository** and **Image Tag** fields on the **nvidia-driver-toolkit** screen provide information about the image that you must download. +The Hypervisor ISO does not include the nvidia-driver-toolkit container image. Because of its size, the image is pulled from Docker Hub by default. If you have an air-gapped environment, you can download and push the image to your private registry. The **Image Repository** and **Image Tag** fields on the **nvidia-driver-toolkit** screen provide information about the image that you must download. -![](/img/v1.3/advanced/nvidia-driver-toolkit.png) +![](/img/v1.2/advanced-hv/nvidia-driver-toolkit.png) :::note -Each new Harvester version will be released with the correct nvidia-driver-toolkit image to ensure that all dependencies required to install the NVIDIA vGPU KVM drivers are available in the image. +Each new Hypervisor version will be released with the correct nvidia-driver-toolkit image to ensure that all dependencies required to install the NVIDIA vGPU KVM drivers are available in the image. ::: To enable the addon, users need to perform the following: diff --git a/versioned_docs/version-v1.6/advanced/addons/seeder.md b/versioned_docs/version-v1.6/advanced/addons/seeder.md index b6dbce25..f1a1b6d5 100644 --- a/versioned_docs/version-v1.6/advanced/addons/seeder.md +++ b/versioned_docs/version-v1.6/advanced/addons/seeder.md @@ -1,14 +1,14 @@ --- sidebar_position: 4 -sidebar_label: Harvester Seeder -title: "Harvester Seeder (Experimental)" +sidebar_label: Hypervisor Seeder +title: "Hypervisor Seeder (Experimental)" keywords: - add-on - addon - out-of-band - harvester-seeder - Seeder -Description: Perform out-of-band operations on Harvester hosts via IPMI and discover hardware events via Redfish +Description: Perform out-of-band operations on Hypervisor hosts via IPMI and discover hardware events via Redfish --- @@ -21,7 +21,7 @@ Description: Perform out-of-band operations on Harvester hosts via IPMI and disc ::: -The **harvester-seeder** add-on allows you to perform out-of-band operations on Harvester hosts using the Intelligent Platform Management Interface (IPMI). +The **harvester-seeder** add-on allows you to perform out-of-band operations on Hypervisor hosts using the Intelligent Platform Management Interface (IPMI). This add-on can also discover hardware and related events for hosts that support [Redfish](https://www.dmtf.org/standards/redfish)-based access, and then associate that hardware with the corresponding hosts. @@ -47,7 +47,7 @@ Ensure that the following requirements are met before enabling the add-on. ## Enabling the Add-On and Configuring Hosts -1. On the Harvester UI, go to **Advanced** > **Add-ons**. +1. On the Hypervisor UI, go to **Advanced** > **Add-ons**. 1. Select **harvester-seeder**, and then select **⋮** > **Enable**. @@ -71,7 +71,7 @@ Ensure that the following requirements are met before enabling the add-on. ## Power-Related Operations -You can use the Harvester UI to shut down and reboot hosts once the Out-of-Band Access settings are configured. However, you must first enable [Maintenance Mode](../../host/host.md#node-maintenance), which automatically migrates all VMs to other nodes. **harvester-seeder** communicates with the hosts via IPMI when performing the selected operation. +You can use the Hypervisor UI to shut down and reboot hosts once the Out-of-Band Access settings are configured. However, you must first enable [Maintenance Mode](../../host/host.md#node-maintenance), which automatically migrates all VMs to other nodes. **harvester-seeder** communicates with the hosts via IPMI when performing the selected operation. ![](/img/v1.2/seeder/ShutdownReboot.png) @@ -81,7 +81,7 @@ You can also power on VMs while Maintenance Mode is enabled. ## Hardware Event Aggregation -If you selected **Enabled** in the **Event** section of the **Out-of-Band Access** settings screen, **harvester-seeder** leverages Redfish to query the hardware for information about component failures and fan temperatures. The information is converted to Kubernetes events during hardware reconciliation and is subsequently handled by the Kubernetes garbage collection policy. Harvester stores these events for 1 hour by default. +If you selected **Enabled** in the **Event** section of the **Out-of-Band Access** settings screen, **harvester-seeder** leverages Redfish to query the hardware for information about component failures and fan temperatures. The information is converted to Kubernetes events during hardware reconciliation and is subsequently handled by the Kubernetes garbage collection policy. Hypervisor stores these events for 1 hour by default. ![](/img/v1.2/seeder/HardwareEvents.png) diff --git a/versioned_docs/version-v1.6/advanced/addons/vmimport.md b/versioned_docs/version-v1.6/advanced/addons/vmimport.md index d8cef9d0..c692cc39 100644 --- a/versioned_docs/version-v1.6/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.6/advanced/addons/vmimport.md @@ -10,7 +10,7 @@ title: "VM Import" _Available as of v1.1.0_ -With the vm-import-controller addon users can import their virtual machines from VMware and OpenStack into Harvester. +With the vm-import-controller addon users can import their virtual machines from VMware and OpenStack into Hypervisor. To use the VM import feature, users need to enable the vm-import-controller addon. @@ -148,7 +148,7 @@ spec: gracefulShutdownTimeoutSeconds: 30 ``` -This will trigger the controller to export the VM named "alpine-export-test" on the VMware source cluster to be exported, processed and recreated into the Harvester cluster. +This will trigger the controller to export the VM named "alpine-export-test" on the VMware source cluster to be exported, processed and recreated into the Hypervisor cluster. The controller checks the configuration before starting the import process, and cancels the import when it detects errors such as unknown [StorageClasses](../storageclass.md) or networks. These checks are enabled by default, but can be disabled by setting `skipPreflightChecks` to `true`. @@ -156,7 +156,7 @@ The duration of the import process depends on the size of the virtual machine. W If the source virtual machine is placed in a folder, you can specify the folder name in the optional `folder` field. -The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. +The list of items in `networkMapping` will define how the source network interfaces are mapped to the Hypervisor Networks. If necessary, you can specify the model of each source network interface individually using the `networkInterfaceModel` field. The valid values are `e1000`, `e1000e`, `ne2k_pci`, `pcnet`, `rtl8139` and `virtio`. Specifying the default interface model using the `defaultNetworkInterfaceModel` field is particularly useful in the following situations: @@ -170,9 +170,9 @@ If a match is not found, each unmatched network interface is attached to the def The `storageClass` field specifies the [StorageClass](../storageclass.md) to be used for images and provisioning persistent volumes during the import process. If not specified, the default StorageClass will be used. -The `defaultDiskBusType` field allows you to specify the bus type for imported disks. Harvester uses this field in the following ways: +The `defaultDiskBusType` field allows you to specify the bus type for imported disks. Hypervisor uses this field in the following ways: -- VMware sources: The value is used only if Harvester is unable to automatically detect the bus type. +- VMware sources: The value is used only if Hypervisor is unable to automatically detect the bus type. - OpenStack sources: The value is used for all imported disks. The valid values are `sata`, `scsi`, `usb`, and `virtio`. If you do not specify a value, `virtio` is used by default. @@ -232,7 +232,7 @@ OpenStack allows users to have multiple instances with the same name. In such a When creating a virtual machine object, the vm-import-controller add-on uses the name of the source virtual machine, which may not meet the Kubernetes object [naming criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). You may need to rename the source virtual machine to allow successful completion of the import. ##### VMware-Based Virtual Machine Without VMware Tools Is Not Migrated -When you attempt to import a VMware-based virtual machine in Harvester v1.6.0, the following occur if [VMware Tools](https://knowledge.broadcom.com/external/article/315382/overview-of-vmware-tools.html) is not installed on the virtual machine: +When you attempt to import a VMware-based virtual machine in Hypervisor v1.6.0, the following occur if [VMware Tools](https://knowledge.broadcom.com/external/article/315382/overview-of-vmware-tools.html) is not installed on the virtual machine: - The vm-import-controller does not gracefully shut down the guest operating system. - When the graceful shutdown period (`gracefulShutdownTimeoutSeconds`) lapses, the vm-import-controller does not force a hard poweroff. @@ -240,6 +240,6 @@ When you attempt to import a VMware-based virtual machine in Harvester v1.6.0, t To address the issue, perform one of the following workarounds: -- Shut down the virtual machine before migrating it to Harvester +- Shut down the virtual machine before migrating it to Hypervisor - In the `VirtualMachineImport` CRD spec, set the `forcePowerOff` field to `true`. - Install VMware Tools or [open-vm-tools](https://knowledge.broadcom.com/external/article?legacyId=2073803). diff --git a/versioned_docs/version-v1.6/advanced/csidriver.md b/versioned_docs/version-v1.6/advanced/csidriver.md index 6e48e7c3..c7a0613c 100644 --- a/versioned_docs/version-v1.6/advanced/csidriver.md +++ b/versioned_docs/version-v1.6/advanced/csidriver.md @@ -89,7 +89,7 @@ For more information, see [Containerized Data Importer (CDI) Settings](./storage 1. Set the **Provisioner** to the third-party CSI driver in the settings. 1. Next, Configure the **Volume Snapshot Class Name**. This setting points to the name of the `VolumeSnapshotClass` used for creating volume snapshots or VM snapshots. -![csi-driver-config-external](/img/v1.5/advanced/csi-driver-config-external.png) +![csi-driver-config-external](/img/v1.5/advanced-hv/csi-driver-config-external.png) ## Use the CSI Driver @@ -101,7 +101,7 @@ You can use an external storage solution to store and manage virtual machine ima When [uploading a virtual machine image](../image/upload-image.md) using the Harvester UI (**Image > Create**), you must select the StorageClass for the external storage solution on the **Storage** tab. In the following example, the StorageClass is **nfs-csi**. -![create-image-with-nfs-csi](/img/v1.5/advanced/create-image-with-nfs-csi.png) +![create-image-with-nfs-csi](/img/v1.5/advanced-hv/create-image-with-nfs-csi.png) Harvester stores the created image in the external storage solution. @@ -318,4 +318,4 @@ spec: start: - multipathd paused: false -``` \ No newline at end of file +``` diff --git a/versioned_docs/version-v1.6/advanced/witness.md b/versioned_docs/version-v1.6/advanced/witness.md index 69514b0d..b597c316 100644 --- a/versioned_docs/version-v1.6/advanced/witness.md +++ b/versioned_docs/version-v1.6/advanced/witness.md @@ -84,7 +84,7 @@ In summary, you must use a StorageClass that matches the cluster configuration. The workaround is to select a non-witness node and then select a NIC that can be used with that specific node. - ![create network config with specific node](/img/v1.5/advanced-hv/create-policy-with-specific-node.png) + ![create network config with specific node](/img/v1.2/advanced-hv/create-policy-with-specific-node.png) ![get uplink](/img/v1.2/advanced-hv/get-uplink.png) You must repeat this procedure for every non-witness node in the cluster. The same uplink settings can be used across nodes. diff --git a/versioned_docs/version-v1.6/airgap.md b/versioned_docs/version-v1.6/airgap.md index 53cfba04..f7adda51 100644 --- a/versioned_docs/version-v1.6/airgap.md +++ b/versioned_docs/version-v1.6/airgap.md @@ -55,7 +55,7 @@ However, it's essential to understand a guest K8s cluster (e.g., RKE2 cluster) c If the **Cloud Provider** option is configured to **Hypervisor** in a guest K8s cluster, it deploys the Hypervisor cloud provider and Container Storage Interface (CSI) driver. -![cluster-registry](/img/v1.2/cluster-registry.png) + As a result, we recommend monitoring each [RKE2 release](https://github.com/rancher/rke2/releases) in your air gapped environment and pulling the required images into your private registry. Please refer to the **Hypervisor CCM & CSI Driver** with RKE2 Releases section on the [Hypervisor support matrix page](https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/harvester-v1-1-2/) for the best Hypervisor cloud provider and CSI driver capability support. diff --git a/versioned_docs/version-v1.6/developer/addon-development.md b/versioned_docs/version-v1.6/developer/addon-development.md index 802d8bf1..31a1d83c 100644 --- a/versioned_docs/version-v1.6/developer/addon-development.md +++ b/versioned_docs/version-v1.6/developer/addon-development.md @@ -4,21 +4,21 @@ title: "Add-on Development Guide" sidebar_position: 1 sidebar_label: Add-on Development Guide keywords: - - Harvester + - Hypervisor - harvester - Add-on Development -Description: How to write your own Harvester add-on +Description: How to write your own Hypervisor add-on --- -Harvester add-ons allow you to enable and disable specific Harvester and third-party components based on your requirements. Add-ons function as a wrapper for the [RKE2 HelmChart resource definition (CRD)](https://docs.rke2.io/helm#using-the-helm-crd). +Hypervisor add-ons allow you to enable and disable specific Hypervisor and third-party components based on your requirements. Add-ons function as a wrapper for the [RKE2 HelmChart resource definition (CRD)](https://docs.rke2.io/helm#using-the-helm-crd). ## Prerequisites -- An existing Harvester cluster +- An existing Hypervisor cluster ## Add-on Specifications @@ -31,7 +31,7 @@ metadata: name: example-add-on # Name of add-on namespace: example-namespace # Namespace where the add-on CRD is deployed and where the associated Kubernetes components will be deployed labels: # Optional add-on labels - Add-on.harvesterhci.io/experimental: "true" # Predefined label used on the Harvester UI to identify add-ons with the "experimental" maturity level + Add-on.harvesterhci.io/experimental: "true" # Predefined label used on the Hypervisor UI to identify add-ons with the "experimental" maturity level spec: enabled: false # Boolean indicating if an add-on should be enabled or disabled on definition repo: https://chartsrepo.com # Helm chart repository containing the Helm chart managed by the add-on @@ -45,7 +45,7 @@ spec: :::note -Experimental add-ons are not directly packaged in Harvester. An example is the [rancher-vcluster](https://github.com/harvester/experimental-addons/blob/main/rancher-vcluster/rancher-vcluster.yaml) add-on. +Experimental add-ons are not directly packaged in Hypervisor. An example is the [rancher-vcluster](https://github.com/harvester/experimental-addons/blob/main/rancher-vcluster/rancher-vcluster.yaml) add-on. ::: diff --git a/versioned_docs/version-v1.6/getting-started/glossary.md b/versioned_docs/version-v1.6/getting-started/glossary.md index 162d6c6b..ca4dc46e 100644 --- a/versioned_docs/version-v1.6/getting-started/glossary.md +++ b/versioned_docs/version-v1.6/getting-started/glossary.md @@ -29,7 +29,7 @@ Guest nodes are managed through a control plane that controls pod-related activi ## **Hypervisor cluster** -Group of integrated physical servers (hosts) on which the Harvester hypervisor is installed. These servers collectively manage compute, memory, and storage resources to provide an environment for running VMs. +Group of integrated physical servers (hosts) on which the Hypervisor hypervisor is installed. These servers collectively manage compute, memory, and storage resources to provide an environment for running VMs. A three-node cluster is required to fully realize the multi-node features of Hypervisor, particularly high availability. Certain versions of Hypervisor allow you to create clusters with two management nodes and one [witness node](../advanced/witness.md) (and optionally, one or more worker nodes). You can also create [single-node clusters](../advanced/singlenodeclusters.md) that support most Hypervisor features (excluding high availability, multi-replica support, and live migration). diff --git a/versioned_docs/version-v1.6/image/upload-image.md b/versioned_docs/version-v1.6/image/upload-image.md index dfd887b9..e6fcbefa 100644 --- a/versioned_docs/version-v1.6/image/upload-image.md +++ b/versioned_docs/version-v1.6/image/upload-image.md @@ -99,7 +99,7 @@ Currently, qcow2, raw, and ISO images are supported. You can upload images from the [**Multi-Cluster Management**](../rancher/virtualization-management.md#importing-harvester-cluster) screen on the **Rancher UI**. When the status of an image is *Uploading* but the progress indicator displays *0%* for an extended period, check the HTTP response status code. *413* indicates that the size of the request body exceeds the limit. -![](/img/v1.3/image-hv/img-413-code.png) + The maximum request body size should be specific to the cluster that is hosting Rancher (for example, RKE2 clusters have a default limit of 1 MB but no such limit exists in K3s clusters). diff --git a/versioned_docs/version-v1.6/rancher/_category_.json b/versioned_docs/version-v1.6/rancher/_category_.json index 0fc48232..3c102d23 100644 --- a/versioned_docs/version-v1.6/rancher/_category_.json +++ b/versioned_docs/version-v1.6/rancher/_category_.json @@ -2,5 +2,6 @@ "position": 14, "label": "Rancher Integration", "collapsible": true, - "collapsed": true -} \ No newline at end of file + "collapsed": true, + "className": "hide-sidebar-item" +} diff --git a/versioned_docs/version-v1.6/rancher/rancher-integration.md b/versioned_docs/version-v1.6/rancher/rancher-integration.md index 7c0f9094..d62a3328 100644 --- a/versioned_docs/version-v1.6/rancher/rancher-integration.md +++ b/versioned_docs/version-v1.6/rancher/rancher-integration.md @@ -23,9 +23,9 @@ For a comprehensive overview of the support matrix, please refer to the [Harvest For the network requirements, please refer to the doc [here](../install/requirements.md#network-requirements). -
+ ![virtualization-management](/img/v1.2/rancher/virtualization-management.png) diff --git a/versioned_docs/version-v1.6/upgrade/automatic.md b/versioned_docs/version-v1.6/upgrade/automatic.md index 3ba2b1f7..a6640d87 100644 --- a/versioned_docs/version-v1.6/upgrade/automatic.md +++ b/versioned_docs/version-v1.6/upgrade/automatic.md @@ -10,6 +10,7 @@ keywords: - rancher - Harvester Upgrade description: Harvester provides two ways to upgrade. Users can either upgrade using the ISO image or upgrade through the UI. +draft: true --- @@ -470,4 +471,4 @@ Related issues: [#7366](https://github.com/harvester/harvester/issues/7366), [#6 [Recurring Longhorn snapshots and backups](https://longhorn.io/docs/1.10.0/snapshots-and-backups/scheduling-backups-and-snapshots) are not integrated into Harvester. If you decide to use this feature, you must disable all **recurring snapshot and backup jobs in Longhorn** before starting the upgrade. -For more information about the incompatibility, see [Scheduling Virtual Machine Backups and Snapshots](../vm/backup-restore.md#scheduling-virtual-machine-backups-and-snapshots). \ No newline at end of file +For more information about the incompatibility, see [Scheduling Virtual Machine Backups and Snapshots](../vm/backup-restore.md#scheduling-virtual-machine-backups-and-snapshots). diff --git a/versioned_docs/version-v1.6/upgrade/troubleshooting.md b/versioned_docs/version-v1.6/upgrade/troubleshooting.md index 6b811ab7..e37ea475 100644 --- a/versioned_docs/version-v1.6/upgrade/troubleshooting.md +++ b/versioned_docs/version-v1.6/upgrade/troubleshooting.md @@ -2,6 +2,7 @@ sidebar_position: 18 sidebar_label: Troubleshooting title: "Troubleshooting" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-1-2-to-v1-2-0.md b/versioned_docs/version-v1.6/upgrade/v1-1-2-to-v1-2-0.md index 166c8949..7d3af4d9 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-1-2-to-v1-2-0.md +++ b/versioned_docs/version-v1.6/upgrade/v1-1-2-to-v1-2-0.md @@ -2,6 +2,7 @@ sidebar_position: 17 sidebar_label: Upgrade from v1.1.2 to v1.2.0 (not recommended) title: "Upgrade from v1.1.2 to v1.2.0 (not recommended)" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-2-0-to-v1-2-1.md b/versioned_docs/version-v1.6/upgrade/v1-2-0-to-v1-2-1.md index 3698e53a..b73ad614 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-2-0-to-v1-2-1.md +++ b/versioned_docs/version-v1.6/upgrade/v1-2-0-to-v1-2-1.md @@ -2,6 +2,7 @@ sidebar_position: 16 sidebar_label: Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1 title: "Upgrade from v1.1.2/v1.1.3/v1.2.0 to v1.2.1" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-2-1-to-v1-2-2.md b/versioned_docs/version-v1.6/upgrade/v1-2-1-to-v1-2-2.md index 803f8fdc..5f08ee8e 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-2-1-to-v1-2-2.md +++ b/versioned_docs/version-v1.6/upgrade/v1-2-1-to-v1-2-2.md @@ -2,6 +2,7 @@ sidebar_position: 15 sidebar_label: Upgrade from v1.2.1 to v1.2.2 title: "Upgrade from v1.2.1 to v1.2.2" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-2-2-to-v1-3-1.md b/versioned_docs/version-v1.6/upgrade/v1-2-2-to-v1-3-1.md index 7f5ee5e5..c07433db 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-2-2-to-v1-3-1.md +++ b/versioned_docs/version-v1.6/upgrade/v1-2-2-to-v1-3-1.md @@ -2,6 +2,7 @@ sidebar_position: 14 sidebar_label: Upgrade from v1.2.2/v1.3.0 to v1.3.1 title: "Upgrade from v1.2.2/v1.3.0 to v1.3.1" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-3-1-to-v1-3-2.md b/versioned_docs/version-v1.6/upgrade/v1-3-1-to-v1-3-2.md index 1f7cfd94..c89b0e4b 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-3-1-to-v1-3-2.md +++ b/versioned_docs/version-v1.6/upgrade/v1-3-1-to-v1-3-2.md @@ -2,6 +2,7 @@ sidebar_position: 13 sidebar_label: Upgrade from v1.3.1 to v1.3.2 title: "Upgrade from v1.3.1 to v1.3.2" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-3-2-to-v1-4-0.md b/versioned_docs/version-v1.6/upgrade/v1-3-2-to-v1-4-0.md index c12dc79d..b84010e3 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-3-2-to-v1-4-0.md +++ b/versioned_docs/version-v1.6/upgrade/v1-3-2-to-v1-4-0.md @@ -2,6 +2,7 @@ sidebar_position: 12 sidebar_label: Upgrade from v1.3.2 to v1.4.0 title: "Upgrade from v1.3.2 to v1.4.0" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-4-0-to-v1-4-1.md b/versioned_docs/version-v1.6/upgrade/v1-4-0-to-v1-4-1.md index ad7d1bfc..924e8054 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-4-0-to-v1-4-1.md +++ b/versioned_docs/version-v1.6/upgrade/v1-4-0-to-v1-4-1.md @@ -2,6 +2,7 @@ sidebar_position: 11 sidebar_label: Upgrade from v1.4.0 to v1.4.1 title: "Upgrade from v1.4.0 to v1.4.1" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-2.md b/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-2.md index 77fc3a88..9d440c0b 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-2.md +++ b/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-2.md @@ -2,6 +2,7 @@ sidebar_position: 10 sidebar_label: Upgrade from v1.4.1 to v1.4.2 title: "Upgrade from v1.4.1 to v1.4.2" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-3.md b/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-3.md index 5aa455cb..f9053c31 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-3.md +++ b/versioned_docs/version-v1.6/upgrade/v1-4-1-to-v1-4-3.md @@ -2,6 +2,7 @@ sidebar_position: 9 sidebar_label: Upgrade from v1.4.1/v1.4.2 to v1.4.3 title: "Upgrade from v1.4.1/v1.4.2 to v1.4.3" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-0.md b/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-0.md index 9c729a8c..5aee430e 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-0.md +++ b/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-0.md @@ -2,6 +2,7 @@ sidebar_position: 8 sidebar_label: Upgrade from v1.4.2/v1.4.3 to v1.5.0 title: "Upgrade from v1.4.2/v1.4.3 to v1.5.0" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-1.md b/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-1.md index df15a0d5..b16db6a7 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-1.md +++ b/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-1.md @@ -2,6 +2,7 @@ sidebar_position: 7 sidebar_label: Upgrade from v1.4.2/v1.4.3 to v1.5.1 title: "Upgrade from v1.4.2/v1.4.3 to v1.5.1" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-2.md b/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-2.md index acfcf9b8..ee332fef 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-2.md +++ b/versioned_docs/version-v1.6/upgrade/v1-4-2-to-v1-5-2.md @@ -2,6 +2,7 @@ sidebar_position: 6 sidebar_label: Upgrade from v1.4.2/v1.4.3 to v1.5.2 title: "Upgrade from v1.4.2/v1.4.3 to v1.5.2" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-1.md b/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-1.md index 6caa884c..4d116eef 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-1.md +++ b/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-1.md @@ -2,6 +2,7 @@ sidebar_position: 5 sidebar_label: Upgrade from v1.5.0 to v1.5.1 title: "Upgrade from v1.5.0 to v1.5.1" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-2.md b/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-2.md index 281cf1cd..3e6b1c87 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-2.md +++ b/versioned_docs/version-v1.6/upgrade/v1-5-0-to-v1-5-2.md @@ -2,6 +2,7 @@ sidebar_position: 4 sidebar_label: Upgrade from v1.5.0/v1.5.1 to v1.5.2 title: "Upgrade from v1.5.0/v1.5.1 to v1.5.2" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-5-x-to-v1-6-x.md b/versioned_docs/version-v1.6/upgrade/v1-5-x-to-v1-6-x.md index 76b407fc..5d831380 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-5-x-to-v1-6-x.md +++ b/versioned_docs/version-v1.6/upgrade/v1-5-x-to-v1-6-x.md @@ -2,6 +2,7 @@ sidebar_position: 3 sidebar_label: Upgrade from v1.5.x to v1.6.x title: "Upgrade from v1.5.x to v1.6.x" +draft: true --- diff --git a/versioned_docs/version-v1.6/upgrade/v1-6-x-to-v1-6-y.md b/versioned_docs/version-v1.6/upgrade/v1-6-x-to-v1-6-y.md index 1084b8ca..7d10f15f 100644 --- a/versioned_docs/version-v1.6/upgrade/v1-6-x-to-v1-6-y.md +++ b/versioned_docs/version-v1.6/upgrade/v1-6-x-to-v1-6-y.md @@ -2,6 +2,7 @@ sidebar_position: 2 sidebar_label: Upgrade from v1.6.x to v1.6.y title: "Upgrade from v1.6.x to v1.6.y" +draft: true --- @@ -96,4 +97,4 @@ This is a rare synchronization failure: the job was already created but the upgr The workaround is to delete the existing post-drain job and then wait for the upgrade controller to recreate it. -Related issue: [#9293](https://github.com/harvester/harvester/issues/9293) \ No newline at end of file +Related issue: [#9293](https://github.com/harvester/harvester/issues/9293) diff --git a/versioned_sidebars/version-v1.6-sidebars.json b/versioned_sidebars/version-v1.6-sidebars.json index 0d76a086..d5bca33d 100644 --- a/versioned_sidebars/version-v1.6-sidebars.json +++ b/versioned_sidebars/version-v1.6-sidebars.json @@ -61,7 +61,7 @@ }, { "type": "category", - "label": "Upgrades", + "label": "Upgrades hapus nanti", "items": [ "api/list-namespaced-upgrade", "api/create-namespaced-upgrade",