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

Part III SUSE Cloud Application Platform Administration

14 Upgrading SUSE Cloud Application Platform

uaa, scf, and Stratos together make up a SUSE Cloud Application Platform release. Maintenance updates are delivered as container images from the SUSE registry and applied with Helm.

15 External Database

By default, internal MariaDB instances serve as the backing databases for internal components of SUSE Cloud Application Platform. These components can be configured to use an external database system, such as a data service offered by a cloud service provider or an existing high availability databas…

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.

17 Creating Admin Users

This chapter provides an overview on how to create additional administrators for your Cloud Application Platform cluster.

18 Managing Passwords

The various components of SUSE Cloud Application Platform authenticate to each other using passwords that are automatically managed by the Cloud Application Platform secrets-generator. The only passwords managed by the cluster administrator are passwords for human users. The administrator may create…

19 Accessing the UAA User Interface

After UAA is deployed successfully, users will not be able to log in to the UAA user interface (UI) with the admin user and the UAA_ADMIN_CLIENT_SECRET credentials. This user is only an OAuth client that is authorized to call UAA REST APIs and will need to create a separate user in the UAA server by…

20 Cloud Controller Database Secret Rotation

The Cloud Controller Database (CCDB) encrypts sensitive information like passwords. By default, the encryption key is generated by SCF, for details see https://github.com/SUSE/scf/blob/2d095a71008c33a23ca39d2ab9664e5602f8707e/container-host-files/etc/scf/config/role-manifest.yml#L1656-L1662. If it i…

21 Backup and Restore

cf-plugin-backup backs up and restores your Cloud Controller Database (CCDB), using the Cloud Foundry command line interface (cf CLI). (See Section 30.1, “Using the cf CLI with SUSE Cloud Application Platform”.)

22 Service Brokers

The Open Service Broker API provides (OSBAPI) your SUSE Cloud Application Platform applications with access to external dependencies and platform-level capabilities, such as databases, filesystems, external repositories, and messaging systems. These resources are called services. Services are create…

23 App-AutoScaler

The App-AutoScaler service is used for automatically managing an application's instance count when deployed on SUSE Cloud Foundry. The scaling behavior is determined by a set of criteria defined in a policy (See Section 23.5, “Policies”).

24 Logging

There are two types of logs in a deployment of SUSE Cloud Application Platform, applications logs and component logs. The following provides a brief overview of each log type and how to retrieve them for monitoring and debugging use.

25 Managing Certificates

This chapter describes the process to deploy SUSE Cloud Application Platform installed with certificates signed by an external Certificate Authority.

26 Integrating CredHub with SUSE Cloud Application Platform

SUSE Cloud Application Platform supports CredHub integration. You should already have a working CredHub instance, a CredHub service on your cluster, then apply the steps in this chapter to connect SUSE Cloud Application Platform.

27 Buildpacks

Buildpacks are used to construct the environment needed to run your applications, including any required runtimes or frameworks as well as other dependencies. When you deploy an application, a buildpack can be specified or automatically detected by cycling through all available buildpacks to find on…

28 Custom Application Domains

In a standard SUSE Cloud Foundry deployment, applications will use the same domain as the one configured in your scf-config-values.yaml for SCF. For example, if DOMAIN is set as example.com in your scf-config-values.yaml and you deploy an application called myapp then the application's URL will be m…

29 Managing Nproc Limits of Pods

It is not recommended to change these values without the guidance of SUSE Cloud Application Platform developers. Please contact support for assistance.