This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.
Important things to know before deploying SUSE Cloud Application Platform.
Schedulers such as Diego and Eirini, and stacks such as
cflinuxfs3 or sle15, have different
memory requirements for applications. Not every combination is tested so
there is no universal memory setting for Cloud Application Platform, and because it depends on the
application deployed, it is up to the user to adjust the setting based on
their application.
During deployment, pods are spawned over time, starting with a single
pod whose name stars with ig-. This pod will eventually
disappear and will be replaced by other pods whose progress
then can be followed as usual.
The whole process can take around 20—30 minutes to finish.
The initial stage may look like this:
tux > kubectl get pods --namespace kubecf
ig-kubecf-f9085246244fbe70-jvg4z 1/21 Running 0 8m28sLater the progress may look like this:
NAME READY STATUS RESTARTS AGE adapter-0 4/4 Running 0 6m45s api-0 0/15 Init:30/63 0 6m38s bits-0 0/6 Init:8/15 0 6m34s bosh-dns-7787b4bb88-2wg9s 1/1 Running 0 7m7s bosh-dns-7787b4bb88-t42mh 1/1 Running 0 7m7s cc-worker-0 0/4 Init:5/9 0 6m36s credhub-0 0/5 Init:6/11 0 6m33s database-0 2/2 Running 0 6m36s diego-api-0 6/6 Running 2 6m38s doppler-0 0/9 Init:7/16 0 6m40s eirini-0 9/9 Running 0 6m37s log-api-0 0/7 Init:6/13 0 6m35s nats-0 4/4 Running 0 6m39s router-0 0/5 Init:5/11 0 6m33s routing-api-0 0/4 Init:5/10 0 6m42s scheduler-0 0/8 Init:8/17 0 6m35s singleton-blobstore-0 0/6 Init:6/11 0 6m46s tcp-router-0 0/5 Init:5/11 0 6m37s uaa-0 0/6 Init:8/13 0 6m36s
Release names (for example, when you run helm install
RELEASE_NAME) have a maximum length of 36 characters.
KubeCF and cf-operator interoperate closely. Before you deploy a specific version combination, make sure they were confirmed to work. For more information see Section 3.4, “Releases and Associated Versions”.
The supported upgrade method is to install all upgrades, in order. Skipping releases is not supported. This table matches the Helm chart versions to each release as well as other version related information.
| CAP Release | cf-operator Helm Chart Version | KubeCF Helm Chart Version | Stratos Helm Chart Version | Stratos Metrics Helm Chart Version | Minimum Kubernetes Version Required | CF API Implemented | Known Compatible CF CLI Version | CF CLI URL |
|---|---|---|---|---|---|---|---|---|
| 2.1.1 (current release) | 7.2.1+0.gaeb6ef3 | 2.7.13 | 4.4.1 | 1.3.0 | 1.14 | 2.144.0 | 6.49.0 | https://github.com/cloudfoundry/cli/releases/tag/v6.49.0 |
| 2.1.0 | 6.1.17+0.gec409fd7 | 2.5.8 | 4.2.0 | 1.3.0 | 1.14 | 2.144.0 | 6.49.0 | https://github.com/cloudfoundry/cli/releases/tag/v6.49.0 |
| 2.0.1 | 4.5.13+.gd4738712 | 2.2.3 | 4.0.1 | 1.2.1 | 1.14 | 2.144.0 | 6.49.0 | https://github.com/cloudfoundry/cli/releases/tag/v6.49.0 |
| 2.0 | 4.5.6+0.gffc6f942 | 2.2.2 | 3.2.1 | 1.2.1 | 1.14 | 2.144.0 | 6.49.0 | https://github.com/cloudfoundry/cli/releases/tag/v6.49.0 |