Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Cloud Application Platform 2.1.1

14 Configuration Changes

After the initial deployment of Cloud Application Platform, any changes made to your Helm chart values, whether through your kubecf-config-values.yaml file or directly using Helm's --set flag, are applied using the helm upgrade command.

Warning
Warning: Do Not Make Changes to Pod Counts During a Version Upgrade

The helm upgrade command can be used to apply configuration changes as well as perform version upgrades to Cloud Application Platform. A change to the pod count configuration should not be applied simultaneously with a version upgrade. Sizing changes should be made separately, either before or after, from a version upgrade.

14.1 Configuration Change Example

Consider an example where you want to enable the App-AutoScaler.

The entry below is added to your kubecf-config-values.yaml file and set with enabled set to true.

features:
  autoscaler:
    enabled: true

The changed is then applied with the helm upgrade command. This example assumes the suse/kubecf Helm chart deployed was named kubecf.

tux > helm upgrade kubecf suse/kubecf \
--namespace kubecf \
--values kubecf-config-values.yaml \
--version 2.7.13

When all pods are in a READY state, the configuration change will also be reflected. Assuming the chart was deployed to the kubecf namespace, progress can be monitored with:

tux > watch --color 'kubectl get pods --namespace kubecf'

14.2 Other Examples

The following are other examples of using helm upgrade to make configuration changes:

Print this page