How to disable autoscaler for rke2-coredns

This document (000021185) is provided subject to the disclaimer at the end of this document.

Environment

RKE2

Situation

RKE2 allows the use of HelmChartConfig resources to customize add-on packages deployed as HelmCharts[1]. This can be used for packages like Canal, CoreDNS, Nginx-Ingress, and so on.

Note: the example below is for standalone RKE2 clusters and not deployed by Rancher

Resolution

A creation of a file under /var/lib/rancher/rke2/server/manifests/ is necessary to disable autoscaler for rke2-coredns. For our case, the file is called rke2-coredns-extraconfig.yaml and it will have the content below. The rke2-server service will restarted to apply the change.

---
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: rke2-coredns
  namespace: kube-system
spec:
  valuesContent: |-
    autoscaler:
      enabled: false

The following can be executed to confirm that the autoscaler pod wasn't created

kubectl -n kube-system get pods | grep autoscaler

The coreDNS or the rke2-coredns package could be downloaded to review the values.yml to determine what could be customized [2][3].

Additional Information

[1] https://docs.rke2.io/helm
[2] https://github.com/rancher/rke2-charts/blob/main-source/packages/rke2-coredns/package.yaml
[3] https://rke2-charts.rancher.io/assets/rke2-coredns/rke2-coredns-1.24.002.tgz

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.