Skip to content

Advanced configuration

To accommodate for more specific needs, KaaS clusters support a range of additionnal configuration options.

Essential cluster components

You can override the default configuration of the following components of your cluster:

  • CoreDNS
  • CNI: Cilium
  • Metrics server

The default configuration can be found here: kaas-essentials

Here is how you can achieve this:

  1. Access your cluster's page under PaaS → Kubernetes.
  2. Click Options → Edit (top right).
  3. Under Advanced Configuration → Cluster Essentials Customization, click on Edit config for the given component and write the configuration overrides in the pop-up window. Expected input are values from the component's Helm chart in YAML format.

For example, to change the amount of CoreDNS replicas you would write: 

replicaCount: 1

  1. Add your custom Helm values under <cluster-name>.kaasEssentials.values.<coredns/cilium/metrics-server>.

For example, to change the amount of CoreDNS replicas you would have: 

my-cluster:
  kaasEssentials:
    values:
      coredns:
        replicaCount: 1

Full chart values: sfs-kaas.

Post-installation Helm chart

You can further automate the setup process of your cluster by pointing to a custom Helm chart which will be applied to the cluster during the installation.

To accomplish this follow these steps:

  1. Access your cluster's page under PaaS → Kubernetes.
  2. Click Options → Edit (top right).
  3. Under Advanced Configuration, enable the Post Installation Chart toggle
  4. Fill out the information about the desired chart:
    • Chart Name
    • Chart Version
    • Namespace: target namespace where the chart should be applied.
    • Repository URL: Source reposistory to pull the chart from.
  5. Click on Helm Chart Values → Edit values and write the configuration overrides for you chart.
  1. Add deployment specification about your chart under <cluster-name>.postInstallChart:
    • chartName
    • chartVersion
    • namespace: target namespace where the chart should be applied.
    • repoUrl: Source reposistory to pull the chart from.
    • revision: Counter that needs to be increased to trigger the re-apply of the chart.

Example for the Traefik ingress and gatewayAPI controller: 

my-cluster:
  postInstallChart:
    chartName: traefik
    chartVersion: 39.0.2
    repoUrl: https://traefik.github.io/charts
    revision: 1
    values:
      # add your values here

Full chart values: sfs-kaas.