Skip to main content

k3s

This currated role installs k3s on the ACE-Box. It also configures kube config to automatically connect to the cluster via kubectl and helm.

For the details, please check this link: https://docs.k3s.io/

Using the role​

Deploy​

- include_role:
    name: k3s

Following variables can be set when applying the role:

---
k3s_version: "v1.29.10+k3s1" # Check https://github.com/k3s-io/k3s/releases
k3s_pod_limit: 110 #Change node pod limit. WARNING: ONLY CHANGE IF NEEDED - Experimental Feature

Note: Changing the pod limit to any value other than 110 is an experimental feature that should only be used when needed! Ensure that the VM has sufficient resources to cater for high pod count (CPU, Memory, Disk). You can consult the Dynatrace Kubernetes App for actual count and resource utilisation information

The role will:

  • Configure ingress_class automatically to use traefik
  • Install helm
  • Deploy and restart k3s
  • Deploy a private registry
  • Configure docker to use the insecure private registry

Following variables will be exposed after installation:

ingress_class: `traefik`
kubernetes_flavour: `k3s`

(Optional) Restart​

There is a restart role that can be used if needed - it is also called when k3s is deployed.

- include_role:
    name: k3s
    tasks_from: restart