The steps in this section describe how to install Stratos on SUSE® CaaS Platform without an external load balancer, instead mapping a worker node to your SUSE Cloud Application Platform domain as described in Section 4.5, “Deployment Configuration”. These instructions assume you have followed the procedure in Chapter 4, Deploying SUSE Cloud Application Platform on SUSE CaaS Platform, have deployed kubecf successfully, and have created a default storage class.

If you are using SUSE Enterprise Storage as your storage back-end, copy the secret into the Stratos namespace:

tux > kubectl get secret ceph-secret-admin --output json --namespace default | \
sed 's/"namespace": "default"/"namespace": "stratos"/' | kubectl create --filename -

You should already have the Stratos charts when you downloaded the SUSE charts repository (see Section 4.12, “Add the Kubernetes Charts Repository”). Search your Helm repository to verify that you have the suse/console chart:

tux > helm search repo suse
NAME                            CHART VERSION        APP VERSION    DESCRIPTION
suse/cf-operator                7.2.1+0.gaeb6ef3    2.1.1          A Helm chart for cf-operator, the k8s operator ....
suse/console                    4.4.1                2.1.1          A Helm chart for deploying SUSE Stratos Console
suse/kubecf                     2.7.13                2.1.1          A Helm chart for KubeCF
suse/metrics                    1.3.0                2.1.1          A Helm chart for Stratos Metrics
suse/minibroker                 1.2.0                               A minibroker for your minikube
suse/nginx-ingress              0.28.4               0.15.0         An nginx Ingress controller that uses ConfigMap to store ...
...

Create a YAML file, called stratos-config-values.yaml in this example, and use it to make configurations to the Stratos Helm chart.

### example Stratos deployment configuration file
### stratos-config-values.yaml

console:
  # Use local admin user instead of UAA
  localAdminPassword: changeme

Note: Technology Preview Features

Some Stratos releases may include features as part of a technology preview. Technology preview features are for evaluation purposes only and not supported for production use. To see the technology preview features available for a given release, refer to https://github.com/SUSE/stratos/blob/master/CHANGELOG.md.

To enable technology preview features, add the console.techPreview Helm value to your stratos-config-values.yaml and set it to true.

### example Stratos deployment configuration file                        
### stratos-config-values.yaml
                                                                                 
console:
  techPreview: true

Create a namespace for your Stratos deployment.

tux > kubectl create namespace stratos

Deploy Stratos using Helm.

tux > helm install susecf-console suse/console \
--namespace stratos \
--values stratos-config-values.yaml

You can monitor the status of your stratos deployment with the watch command:

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

When stratos is successfully deployed, the following is observed:

Press Ctrl–C to exit the watch command.

When the stratos deployment completes, query with Helm to view your release information:

tux > helm status susecf-console
LAST DEPLOYED: Wed Mar 27 06:51:36 2019
NAMESPACE: stratos
STATUS: DEPLOYED

RESOURCES:
==> v1/Secret
NAME                           TYPE    DATA  AGE
susecf-console-secret          Opaque  2     3h
susecf-console-mariadb-secret  Opaque  2     3h

==> v1/PersistentVolumeClaim
NAME                                  STATUS  VOLUME                                    CAPACITY  ACCESSMODES  STORAGECLASS  AGE
susecf-console-upgrade-volume         Bound   pvc-711380d4-5097-11e9-89eb-fa163e15acf0  20Mi      RWO          persistent    3h
susecf-console-encryption-key-volume  Bound   pvc-711b5275-5097-11e9-89eb-fa163e15acf0  20Mi      RWO          persistent    3h
console-mariadb                       Bound   pvc-7122200c-5097-11e9-89eb-fa163e15acf0  1Gi       RWO          persistent    3h

==> v1/Service
NAME                    CLUSTER-IP      EXTERNAL-IP                                                PORT(S)   AGE
susecf-console-mariadb  172.24.137.195  <none>                                                     3306/TCP  3h
susecf-console-ui-ext   172.24.80.22    10.86.101.115,172.28.0.31,172.28.0.36,172.28.0.7,172.28.0.22  8443/TCP  3h

==> v1beta1/Deployment
NAME        DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
stratos-db  1        1        1           1          3h

==> v1beta1/StatefulSet
NAME     DESIRED  CURRENT  AGE
stratos  1        1        3h

Find the external IP address with kubectl get service susecf-console-ui-ext --namespace stratos to access your new Stratos Web console, for example https://10.86.101.115:8443, or use the domain you created for it, and its port, for example https://example.com:8443. Proceed past the warnings about the self-signed certificates and log in as admin with the password you created in stratos-config-values.yaml

Figure 8.1: Stratos UI Cloud Foundry Console #

8.1.1 Connecting SUSE® CaaS Platform to Stratos #

• File Name: cap_depl_stratos.xml
• ID: sec-cap-stratos-caasp-connect

Stratos can show information from your SUSE® CaaS Platform environment.

To enable this, you must register and connect your SUSE® CaaS Platform environment with Stratos.

In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view - you should be shown the "Register new Endpoint" view.

1. In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view.

2. On the Register a new Endpoint view, click the SUSE CaaS Platform button.

3. Enter a memorable name for your SUSE® CaaS Platform environment in the Name field. For example, my-endpoint.

4. Enter the URL of the API server for your Kubernetes environment in the Endpoint Address field. Run kubectl cluster-info and use the value of Kubernetes master as the URL.

   tux > kubectl cluster-info

5. Activate the Skip SSL validation for the endpoint check box if using self-signed certificates.

6. Click Register.

7. Activate the Connect to my-endpoint now (optional). check box.

8. Provide a valid kubeconfig file for your SUSE® CaaS Platform environment.

9. Click Connect.

10. In the Stratos UI, go to Kubernetes in the left-hand side navigation. Information for your SUSE® CaaS Platform environment should now be displayed as in the following figure.

Figure 8.2: Kubernetes Environment Information on Stratos #

Before deploying Stratos, ensure kubecf has been successfully deployed on Amazon EKS (see Chapter 6, Deploying SUSE Cloud Application Platform on Amazon Elastic Kubernetes Service (EKS)).

Configure a scoped storage class for your Stratos deployment. Create a configuration file, called scoped-storage-class.yaml in this example, using the following as a template. Specify the region you are using as the zone and be sure to include the letter (for example, the letter a in us-west-2a) identifier to indicate the Availability Zone used:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: gp2scoped
provisioner: kubernetes.io/aws-ebs
parameters:
  type: gp2
  zone: "us-west-2a"
reclaimPolicy: Retain
mountOptions:
  - debug

Create the storage class using the scoped-storage-class.yaml configuration file:

tux > kubectl create --filename scoped-storage-class.yaml

Verify the storage class has been created:

tux > kubectl get storageclass
NAME            PROVISIONER             AGE
gp2 (default)   kubernetes.io/aws-ebs   1d
gp2scoped       kubernetes.io/aws-ebs   1d

Create a YAML file, called stratos-config-values.yaml in this example, and use it to make configurations to the Stratos Helm chart.

### example Stratos deployment configuration file
### stratos-config-values.yaml

console:
  # Use local admin user instead of UAA
  localAdminPassword: changeme

services:
  loadbalanced: true

kube:
  storage_class:
    persistent: gp2scoped

Note: Technology Preview Features

Some Stratos releases may include features as part of a technology preview. Technology preview features are for evaluation purposes only and not supported for production use. To see the technology preview features available for a given release, refer to https://github.com/SUSE/stratos/blob/master/CHANGELOG.md.

To enable technology preview features, add the console.techPreview Helm value to your stratos-config-values.yaml and set it to true.

### example Stratos deployment configuration file                        
### stratos-config-values.yaml
                                                                                 
console:
  techPreview: true

Create a namespace for your Stratos deployment.

tux > kubectl create namespace stratos

Deploy Stratos using Helm.

tux > helm install susecf-console suse/console
\
--namespace stratos \
--values stratos-config-values.yaml

You can monitor the status of your stratos deployment with the watch command:

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

When stratos is successfully deployed, the following is observed:

Press Ctrl–C to exit the watch command.

Obtain the host name of the service exposed through the public load balancer:

tux > kubectl get service susecf-console-ui-ext --namespace stratos

Use this host name to create a CNAME record. After the record is created, access the console in a web browser by navigating to the domain mapped to the host name of the service retrieved from the kubectl get service step. Upon successfully logging in, you should see something similar to the following figure.

Figure 8.3: Stratos UI Cloud Foundry Console #

8.2.1 Connecting Amazon EKS to Stratos #

• File Name: cap_depl_stratos.xml
• ID: sec-cap-stratos-eks-connect

Stratos can show information from your Amazon EKS environment.

To enable this, you must register and connect your Amazon EKS environment with Stratos.

In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view - you should be shown the "Register new Endpoint" view.

1. In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view.

2. On the Register a new Endpoint view, click the Amazon EKS button.

3. Enter a memorable name for your Amazon EKS environment in the Name field. For example, my-endpoint.

4. Enter the URL of the API server for your Kubernetes environment in the Endpoint Address field. Run kubectl cluster-info and use the value of Kubernetes master as the URL.

   tux > kubectl cluster-info

5. Activate the Skip SSL validation for the endpoint check box if using self-signed certificates.

6. Click Register.

7. Activate the Connect to my-endpoint now (optional). check box.

8. Enter the name of your Amazon EKS cluster in the Cluster field.

9. Enter your AWS Access Key ID in the Access Key ID field.

10. Enter your AWS Secret Access Key in the Secret Access Key field.

11. Click Connect.

12. In the Stratos UI, go to Kubernetes in the left-hand side navigation. Information for your Amazon EKS environment should now be displayed as in the following figure.

Figure 8.4: Kubernetes Environment Information on Stratos #

Before deploying Stratos, ensure kubecf has been successfully deployed on Microsoft AKS (see Chapter 5, Deploying SUSE Cloud Application Platform on Microsoft Azure Kubernetes Service (AKS)).

Create a YAML file, called stratos-config-values.yaml in this example, and use it to make configurations to the Stratos Helm chart.

### example Stratos deployment configuration file
### stratos-config-values.yaml

console:
  # Use local admin user instead of UAA
  localAdminPassword: changeme

services:
  loadbalanced: true

Note: Technology Preview Features

Some Stratos releases may include features as part of a technology preview. Technology preview features are for evaluation purposes only and not supported for production use. To see the technology preview features available for a given release, refer to https://github.com/SUSE/stratos/blob/master/CHANGELOG.md.

To enable technology preview features, add the console.techPreview Helm value to your stratos-config-values.yaml and set it to true.

### example Stratos deployment configuration file                        
### stratos-config-values.yaml
                                                                                 
console:
  techPreview: true

Create a namespace for your Stratos deployment.

tux > kubectl create namespace stratos

Deploy Stratos using Helm.

tux > helm install susecf-console suse/console
\
--namespace stratos \
--values stratos-config-values.yaml

You can monitor the status of your stratos deployment with the watch command:

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

When stratos is successfully deployed, the following is observed:

Press Ctrl–C to exit the watch command.

Obtain the IP address of the service exposed through the public load balancer:

tux > kubectl get service susecf-console-ui-ext --namespace stratos

Use this IP address to create an A record. After the record is created, access the console in a web browser by navigating to the domain mapped to the IP address of the service retrieved from the kubectl get service step. Upon successfully logging in, you should see something similar to the following figure.

Figure 8.5: Stratos UI Cloud Foundry Console #

8.3.1 Connecting Microsoft AKS to Stratos #

• File Name: cap_depl_stratos.xml
• ID: sec-cap-stratos-aks-connect

Stratos can show information from your Microsoft AKS environment.

To enable this, you must register and connect your Microsoft AKS environment with Stratos.

In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view - you should be shown the "Register new Endpoint" view.

1. In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view.

2. On the Register a new Endpoint view, click the Azure AKS button.

3. Enter a memorable name for your Microsoft AKS environment in the Name field. For example, my-endpoint.

4. Enter the URL of the API server for your Kubernetes environment in the Endpoint Address field. Run kubectl cluster-info and use the value of Kubernetes master as the URL.

   tux > kubectl cluster-info

5. Activate the Skip SSL validation for the endpoint check box if using self-signed certificates.

6. Click Register.

7. Activate the Connect to my-endpoint now (optional). check box.

8. Provide a valid kubeconfig file for your Microsoft AKS environment.

9. Click Connect.

10. In the Stratos UI, go to Kubernetes in the left-hand side navigation. Information for your Microsoft AKS environment should now be displayed as in the following figure.

Figure 8.6: Kubernetes Environment Information on Stratos #

Before deploying Stratos, ensure kubecf has been successfully deployed on Google GKE (see Chapter 7, Deploying SUSE Cloud Application Platform on Google Kubernetes Engine (GKE)).

Create a YAML file, called stratos-config-values.yaml in this example, and use it to make configurations to the Stratos Helm chart.

### example Stratos deployment configuration file
### stratos-config-values.yaml

console:
  # Use local admin user instead of UAA
  localAdminPassword: changeme

services:
  loadbalanced: true

Note: Technology Preview Features

Some Stratos releases may include features as part of a technology preview. Technology preview features are for evaluation purposes only and not supported for production use. To see the technology preview features available for a given release, refer to https://github.com/SUSE/stratos/blob/master/CHANGELOG.md.

To enable technology preview features, add the console.techPreview Helm value to your stratos-config-values.yaml and set it to true.

### example Stratos deployment configuration file                        
### stratos-config-values.yaml
                                                                                 
console:
  techPreview: true

Create a namespace for your Stratos deployment.

tux > kubectl create namespace stratos

Deploy Stratos using Helm.

tux > helm install susecf-console suse/console
\
--namespace stratos \
--values stratos-config-values.yaml

You can monitor the status of your stratos deployment with the watch command:

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

When stratos is successfully deployed, the following is observed:

Press Ctrl–C to exit the watch command.

Obtain the IP address of the service exposed through the public load balancer:

tux > kubectl get service susecf-console-ui-ext --namespace stratos

Use this IP address to create an A record. After the record is created, access the console in a web browser by navigating to the domain mapped to the IP address of the service retrieved from the kubectl get service step. Upon successfully logging in, you should see something similar to the following figure.

Figure 8.7: Stratos UI Cloud Foundry Console #

8.4.1 Connecting Google GKE to Stratos #

• File Name: cap_depl_stratos.xml
• ID: sec-cap-stratos-gke-connect

Stratos can show information from your Google GKE environment.

To enable this, you must register and connect your Google GKE environment with Stratos.

In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view - you should be shown the "Register new Endpoint" view.

1. In the Stratos UI, go to Endpoints in the left-hand side navigation and click on the + icon in the top-right of the view.

2. On the Register a new Endpoint view, click the Google Kubernetes Engine button.

3. Enter a memorable name for your Microsoft AKS environment in the Name field. For example, my-endpoint.

4. Enter the URL of the API server for your Kubernetes environment in the Endpoint Address field. Run kubectl cluster-info and use the value of Kubernetes master as the URL.

   tux > kubectl cluster-info

5. Activate the Skip SSL validation for the endpoint check box if using self-signed certificates.

6. Click Register.

7. Activate the Connect to my-endpoint now (optional). check box.

8. Provide a valid Application Default Credentials file for your Google GKE environment. Generate the file using the command below. The command saves the credentials to a file named application_default_credentials.json and outputs the path of the file.

   tux > gcloud auth application-default login

9. Click Connect.

10. In the Stratos UI, go to Kubernetes in the left-hand side navigation. Information for your Google GKE environment should now be displayed as in the following figure.

Figure 8.8: Kubernetes Environment Information on Stratos #

For instructions to upgrade Stratos, follow the process described in Chapter 13, Upgrading SUSE Cloud Application Platform. Take note that kubecf is upgraded prior to upgrading Stratos.

Stratos Metrics provides a Helm chart for deploying Prometheus (see https://prometheus.io/) and the following metrics exporters to Kubernetes:

The Stratos Metrics Helm chart deploys a Prometheus server and the configured Exporters and fronts the Prometheus server with an nginx server to provide authenticated access to Prometheus (currently basic authentication over HTTPS).

When required by configuration, it also contains an initialization script that will setup users in the UAA that have correct scopes/permissions to be able to read data from the Cloud Foundry Firehose and/or API.

Lastly, the Helm chart generates a small metadata file in the root of the nginx server that is used by Stratos to determine which Cloud Foundry and Kubernetes clusters the Prometheus server is providing Metrics for.

To learn more about Stratos Metrics and its full list of configuration options, see https://github.com/SUSE/stratos-metrics.

firehoseExporter:
  instances: 1

cloudFoundry:
  apiEndpoint: https://api.example.com
  uaaAdminClient: admin
  uaaAdminClientSecret: password
  skipSslVerification: "true"
env:
  DOPPLER_PORT: 443
kubernetes:
  apiEndpoint: kube_server_address.example.com
metrics:
  username: username
  password: password
prometheus:
  kubeStateMetrics:
    enabled: true
  server:
    storageClass: "persistent"
services:
  loadbalanced: true

tux > kubectl get secret ceph-secret-admin --output json --namespace default | \
sed 's/"namespace": "default"/"namespace": "metrics"/' | kubectl create --filename -

tux > kubectl create namespace metrics

tux > helm install susecf-metrics suse/metrics \
--namespace metrics \
--values kubecf-config-values.yaml \
--values stratos-metrics-values.yaml

$ watch --color 'kubectl get pods --namespace metrics'