Skip to main content

MicroK8s

Support Lifecycle​

We support different Kubernetes distributions, such as MicroK8s, K3s, and RKE2, until their official End-of-Life (EOL). The EOL is set by the respective owner. Once we stop supporting the minor version, we initiate the deprecation process. Refer to the Kubernetes Support Lifecycle guide to learn more.

tech preview
This is a Tech Preview feature and is subject to change. Do not use this feature in production workloads.

Versions Supported​

Container Network Interface (CNI)​

MicroK8s clusters use the Calico CNI by default. However, this default installation was disabled due to Palette's requirement for a CNI layer to be present in the cluster profiles. This way, users can choose their preferred CNI layer during the cluster profile creation.

Upgrade Strategy​

The upgrade strategy describes how to replace existing control plane nodes with new ones during upgrades.

You can specify the upgrade strategy during cluster profile creation by editing the value of the upgradeStrategy parameter in the MicroK8s pack YAML file displayed under the Pack Details section.

The MicroK8s pack supports three types of upgrade strategies:

  • InPlaceUpgrade - Performs an in-place upgrade of the control plane. For clusters with one control plane and one worker node, InPlaceUpgrade temporarily shuts down the API server.

  • RollingUpgrade - The default upgrade strategy that deletes the current control plane node before creating a new one.

  • SmartUpgrade - Performs an in-place upgrade of the control plane on clusters with fewer than three control plane nodes, and a rolling upgrade on clusters with three or more control plane nodes.

Terraform​

You can reference the MicroK8s pack in Terraform with the following data resource.

data "spectrocloud_registry" "public_registry" {
  name = "Public Repo"
}

data "spectrocloud_pack" "k8s" {
  name    = "kubernetes-microk8s"
  version = "1.27"
  registry_uid = data.spectrocloud_registry.public_registry.id
}