Deployment, Administration, and User Guides
- About This Guide
- I Overview of SUSE Cloud Application Platform
- II Deploying SUSE Cloud Application Platform
- 3 Deployment and Administration Notes
- 4 Deploying SUSE Cloud Application Platform on SUSE CaaS Platform
- 5 Deploying SUSE Cloud Application Platform on Microsoft Azure Kubernetes Service (AKS)
- 6 Deploying SUSE Cloud Application Platform on Amazon Elastic Kubernetes Service (EKS)
- 7 Deploying SUSE Cloud Application Platform on Google Kubernetes Engine (GKE)
- 8 Installing the Stratos Web Console
- 9 Eirini
- 10 Deploying SUSE Cloud Application Platform Using Terraform
- 11 Setting Up a Registry for an Air Gapped Environment
- 12 SUSE Private Registry
- III SUSE Cloud Application Platform Administration
- 13 Upgrading SUSE Cloud Application Platform
- 14 Configuration Changes
- 15 Creating Admin Users
- 16 Managing Passwords
- 17 Accessing the UAA User Interface
- 18 Container Memory Limits and Requests
- 19 Cloud Controller Database Secret Rotation
- 20 Rotating Automatically Generated Secrets
- 21 Backup and Restore
- 22 Service Brokers
- 23 App-AutoScaler
- 24 Integrating CredHub with SUSE Cloud Application Platform
- 25 Buildpacks
- IV SUSE Cloud Application Platform User Guide
- V Troubleshooting
- A Appendix
- B GNU Licenses
14 Configuration Changes #
- File Name: cap_admin_configuration_changes.xml
- ID:
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: 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 #
- File Name: cap_admin_configuration_changes.xml
- ID: sec-cap-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 #
- File Name: cap_admin_configuration_changes.xml
- ID: sec-cap-configuration-change-other-examples
The following are other examples of using helm upgrade to
make configuration changes:
Secrets rotation (see Chapter 20, Rotating Automatically Generated Secrets)
Enabling additional services (see Section 23.2, “Enabling and Disabling the App-AutoScaler Service”)