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

16 Configuration Changes

After the initial deployment of Cloud Application Platform, any changes made to your Helm chart values, whether through your scf-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 (see Section 7.1, “Configuring Cloud Application Platform for High Availability”).

16.1 Configuration Change Example

Consider an example where more granular log entries are required than those provided by your default deployment of uaa; (default LOG_LEVEL: "info").

You would then add an entry for LOG_LEVEL to the env section of your scf-config-values.yaml used to deploy uaa:

env:
  LOG_LEVEL: "debug2"

Then apply the change with the helm upgrade command. This example assumes the suse/uaa Helm chart deployed was named susecf-uaa:

tux > helm upgrade susecf-uaa suse/uaa \
--values scf-config-values.yaml \
--version 2.20.3

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

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

16.2 Other Examples

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

Print this page