This is unreleased documentation for SUSE® Virtualization v1.9 (Dev).

Rancher K3k Addon

rancher-k3k is an Experimental add-on. It is not included in the SUSE Virtualization ISO, but you can download the manifest (rancher-k3k-addon.yaml) from the SUSE Virtualization Releases page. Manifest source files are located in the addons/standalone directory of the SUSE Virtualization repository. For more information about experimental features, see Feature Labels.

The rancher-k3k add-on allows you to run Rancher as a workload on the underlying SUSE Virtualization cluster and is implemented using k3k.

The add-on runs a nested K3s cluster in the rancher-k3k namespace and deploys Rancher to this cluster.

During the installation, the ingress for Rancher is synced to the SUSE Virtualization cluster, allowing end users to access Rancher.

Installing the Add-on

If you are using the SUSE Virtualization kubeconfig file, you can install the add-on by running the following commands:

Install k3k Add-on

kubectl apply -f https://github.com/harvester/harvester/releases/download/<version>/k3k-addon.yaml

Install rancher-k3k Add-on

kubectl apply -f https://github.com/harvester/harvester/releases/download/<version>/rancher-k3k-addon.yaml

Replace <version> with the version of your Harvester cluster (for example, v1.10.0).

Configuring the Add-on

After installation, configure the add-on using the SUSE Virtualization UI.

  1. Go to Advanced > Add-ons.

  2. Locate the k3k add-on, and then select ⋮ > Enable.

  3. Wait a few minutes for the add-on to be deployed and marked ready.

  4. Locate the rancher-k3k add-on, and then select ⋮ > Edit Yaml.

  5. Change the fields hostname, bootstrapPassword in valuesContent section

    spec:
      chart: rancher-k3k
      enabled: false
      repo: https://charts.harvesterhci.io
      valuesContent: |-
        certManagerVersion: "v1.20.2"
        rancher:
          hostname: ""
          version: "v2.14.0"
          replicas: 1
          bootstrapPassword: "password"
        k3kCluster:
          servers: 1
          version: v1.35.4-k3s1
          storageClassName: "harvester-longhorn"
      version: 1.9.1
  6. Save changes and then select ⋮ > Enable.

Once the add-on is deployed, Rancher can take a few minutes to become available.

You can then access Rancher via the hostname DNS record that you provided.

See Rancher Integration for more information.

rancher-k3k is deployed on a k3k cluster with Rancher bootstrapped as part of cluster init.

When you disable the add-on, the PVC remains in the rancher-k3k namespace. If you enable the add-on again, the PVC is reused and Rancher’s previous state is restored.

Before you wipe the data, ensure that the PVC is deleted.