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

6 Installing the Stratos Web Console

The Stratos user interface (UI) is a modern web-based management application for Cloud Foundry. It provides a graphical management console for both developers and system administrators. Install Stratos with Helm after all of the uaa and scf pods are running.

6.1 Deploy Stratos on SUSE® CaaS Platform

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 5.5, “Deployment Configuration”. These instructions assume you have followed the procedure in Chapter 5, Deploying SUSE Cloud Application Platform on SUSE CaaS Platform, have deployed uaa and scf 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 5.6, “Add the Kubernetes Charts Repository”). Search your Helm repository to verify that you have the suse/console chart:

tux > helm search suse
NAME                            CHART VERSION   APP VERSION     DESCRIPTION
suse/cf                         2.20.3          1.5.2           A Helm chart for SUSE Cloud Foundry
suse/cf-usb-sidecar-mysql       1.0.1                           A Helm chart for SUSE Universal Service Broker Sidecar fo...
suse/cf-usb-sidecar-postgres    1.0.1                           A Helm chart for SUSE Universal Service Broker Sidecar fo...
suse/console                    3.1.0           1.5.2           A Helm chart for deploying Stratos UI Console
suse/log-agent-rsyslog      	1.0.1        	8.39.0     	Log Agent for forwarding logs of K8s control pl...
suse/metrics                    1.1.2           1.5.2           A Helm chart for Stratos Metrics
suse/minibroker                 0.3.1                           A minibroker for your minikube
suse/nginx-ingress              0.28.4          0.15.0          An nginx Ingress controller that uses ConfigMap to store ...
suse/uaa                        2.20.3          1.5.2           A Helm chart for SUSE UAA

Use Helm to install Stratos, using the same scf-config-values.yaml configuration file you used to deployuaa and scf:

Important
Important: Non-default SUSE Cloud Foundry namespace

If you used a non-default namespace for SUSE Cloud Foundry, you need to change the UAA_ZONE environment variable in the scf-config-values.yaml to the correct namespace. You can do so in the env section:

 env:
   # Enter the domain you created for your CAP cluster
   DOMAIN: example.com

   # uaa host and port
   UAA_HOST: uaa.example.com
   UAA_PORT: 2793
   # scf namespace, default is "scf"
   UAA_ZONE: scf2
Note
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, set the console.techPreview Helm value to true . For example, when running helm install add --set console.techPreview=true.

tux > helm install suse/console \
    --name susecf-console \
    --namespace stratos \
    --values scf-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:

  • For the volume-migration pod, the STATUS is Completed and the READY column is at 0/1.

  • All other pods have a Running STATUS and a READY value of n/n.

Press CtrlC 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. Wade through the nag screens about the self-signed certificates and log in as admin with the password you created in scf-config-values.yaml.

Stratos UI Cloud Foundry Console
Figure 6.1: Stratos UI Cloud Foundry Console

6.1.1 Connecting SUSE® CaaS Platform to Stratos

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.

Kubernetes Environment Information on Stratos
Figure 6.2: Kubernetes Environment Information on Stratos

6.2 Deploy Stratos on Amazon EKS

Before deploying Stratos, ensure uaa and scf have been successfully deployed on Amazon EKS (see Chapter 10, 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

Use Helm to install Stratos:

Important
Important: Non-default SUSE Cloud Foundry namespace

If you used a non-default namespace for SUSE Cloud Foundry, you need to change the UAA_ZONE environment variable in the scf-config-values.yaml to the correct namespace. You can do so in the env section:

 env:
   # Enter the domain you created for your CAP cluster
   DOMAIN: example.com

   # uaa host and port
   UAA_HOST: uaa.example.com
   UAA_PORT: 2793
   # scf namespace, default is "scf"
   UAA_ZONE: scf2
Note
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, set the console.techPreview Helm value to true . For example, when running helm install add --set console.techPreview=true.

tux > helm install suse/console \
    --name susecf-console \
    --namespace stratos \
    --values scf-config-values.yaml \
    --set kube.storage_class.persistent=gp2scoped \
    --set services.loadbalanced=true

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:

  • For the volume-migration pod, the STATUS is Completed and the READY column is at 0/1.

  • All other pods have a Running STATUS and a READY value of n/n.

Press CtrlC 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.

Stratos UI Cloud Foundry Console
Figure 6.3: Stratos UI Cloud Foundry Console

6.2.1 Connecting Amazon EKS to Stratos

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.

Kubernetes Environment Information on Stratos
Figure 6.4: Kubernetes Environment Information on Stratos

6.3 Deploy Stratos on Microsoft AKS

Before deploying Stratos, ensure uaa and scf have been successfully deployed on Microsoft AKS (see Chapter 9, Deploying SUSE Cloud Application Platform on Microsoft Azure Kubernetes Service (AKS)).

Important
Important: Non-default SUSE Cloud Foundry namespace

If you used a non-default namespace for SUSE Cloud Foundry, you need to change the UAA_ZONE environment variable in the scf-config-values.yaml to the correct namespace. You can do so in the env section:

 env:
   # Enter the domain you created for your CAP cluster
   DOMAIN: example.com

   # uaa host and port
   UAA_HOST: uaa.example.com
   UAA_PORT: 2793
   # scf namespace, default is "scf"
   UAA_ZONE: scf2
Note
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, set the console.techPreview Helm value to true . For example, when running helm install add --set console.techPreview=true.

Use Helm to install Stratos:

tux > helm install suse/console \
    --name susecf-console \
    --namespace stratos \
    --values scf-config-values.yaml \
    --set services.loadbalanced=true

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:

  • For the volume-migration pod, the STATUS is Completed and the READY column is at 0/1.

  • All other pods have a Running STATUS and a READY value of n/n.

Press CtrlC 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.

Stratos UI Cloud Foundry Console
Figure 6.5: Stratos UI Cloud Foundry Console

6.3.1 Connecting Microsoft AKS to Stratos

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.

Kubernetes Environment Information on Stratos
Figure 6.6: Kubernetes Environment Information on Stratos

6.4 Deploy Stratos on Google GKE

Before deploying Stratos, ensure uaa and scf have been successfully deployed on Google GKE (see Chapter 11, Deploying SUSE Cloud Application Platform on Google Kubernetes Engine (GKE)).

Use Helm to install Stratos:

Important
Important: Non-default SUSE Cloud Foundry namespace

If you used a non-default namespace for SUSE Cloud Foundry, you need to change the UAA_ZONE environment variable in the scf-config-values.yaml to the correct namespace. You can do so in the env section:

 env:
   # Enter the domain you created for your CAP cluster
   DOMAIN: example.com

   # uaa host and port
   UAA_HOST: uaa.example.com
   UAA_PORT: 2793
   # scf namespace, default is "scf"
   UAA_ZONE: scf2
Note
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, set the console.techPreview Helm value to true . For example, when running helm install add --set console.techPreview=true.

tux > helm install suse/console \
    --name susecf-console \
    --namespace stratos \
    --values scf-config-values.yaml \
    --set services.loadbalanced=true

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:

  • For the volume-migration pod, the STATUS is Completed and the READY column is at 0/1.

  • All other pods have a Running STATUS and a READY value of n/n.

Press CtrlC 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.

Stratos UI Cloud Foundry Console
Figure 6.7: Stratos UI Cloud Foundry Console

6.4.1 Connecting Google GKE to Stratos

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.

Kubernetes Environment Information on Stratos
Figure 6.8: Kubernetes Environment Information on Stratos

6.5 Upgrading Stratos

For instructions to upgrade Stratos, follow the process described in Chapter 14, Upgrading SUSE Cloud Application Platform. Take note that uaa and scf, other components along with Stratos that make up a Cloud Application Platform release, are upgraded prior to upgrading Stratos.

6.6 Stratos Metrics

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

  • Cloud Foundry Firehose Exporter (enabled by default)

  • Cloud Foundry Exporter (disabled by default)

  • Kubernetes State Metrics Exporter (disabled by default)

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.

6.6.1 Exporter Configuration

6.6.1.1 Firehose Exporter

This exporter can be enabled/disabled via the Helm value firehoseExporter.enabled. By default this exporter is enabled.

You must provide the following Helm chart values for this Exporter to work correctly:

  • cloudFoundry.apiEndpoint - API Endpoint of the Cloud Foundry API Server

  • cloudFoundry.uaaAdminClient - Admin client of the UAA used by the Cloud Foundry server

  • cloudFoundry.uaaAdminClientSecret - Admin client secret of the UAA used by the Cloud Foundry server

  • cloudFoundry.skipSslVerification - Whether to skip SSL verification when communicating with Cloud Foundry and the UAA APIs

You can scale the firehose nozzle in Stratos Metrics by specifying the following override:

firehoseExporter:
  instances: 1

Please note, the number of firehose nozzles should be proportional to the number of Traffic Controllers in your Cloud Foundry (see docs at https://docs.cloudfoundry.org/loggregator/log-ops-guide.html). Otherwise, Loggregator will not split the firehose between the nozzles.

6.6.1.2 Cloud Foundry Exporter

This exporter can be enabled/disabled via the Helm value cfExporter.enabled. By default this exporter is disabled.

You must provide the following Helm chart values for this Exporter to work correctly:

  • cloudFoundry.apiEndpoint - API Endpoint of the Cloud Foundry API Server

  • cloudFoundry.uaaAdminClient - Admin client of the UAA used by the Cloud Foundry server

  • cloudFoundry.uaaAdminClientSecret - Admin client secret of the UAA used by the Cloud Foundry server

  • cloudFoundry.skipSslVerification - Whether to skip SSL verification when communicating with Cloud Foundry and the UAA APIs

6.6.1.3 Kubernetes Monitoring

This exporter can be enabled/disabled via the Helm value prometheus.kubeStateMetrics.enabled. By default this exporter is disabled.

You must provide the following Helm chart values for this Exporter to work correctly:

  • kubernetes.apiEndpoint - The API Endpoint of the Kubernetes API Server

6.6.2 Install Stratos Metrics with Helm

In order to display metrics data with Stratos, you need to deploy the stratos-metrics Helm chart. As with deploying Stratos, you should deploy the metrics Helm chart using the same scf-config-values.yaml file that was used for deploying scf and uaa.

Additionally, create a new YAML file, named stratos-metrics-values.yaml in this example, for configuration options specific to Stratos Metrics.

The following is an example stratos-metrics-values.yaml file.

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

where:

  • kubernetes.apiEndpoint is the same URL that you used when registering your Kubernetes environment with Stratos (the Kubernetes API Server URL).

  • prometheus.server.storageClass is the storage class to be used by Stratos Metrics. If a storage class is not assigned, the default storage class will be used. If a storage class is not specified and there is no default storage class, the prometheus pod will fail to start.

  • metrics.username is the username used to authenticate with the nginx server that fronts Prometheus. This username is also used during the Section 6.6.3, “Connecting Stratos Metrics”) process.

  • metrics.password is the password used to authenticate with the nginx server that fronts Prometheus. This username is also used during the Section 6.6.3, “Connecting Stratos Metrics”) process. Ensure a secure password is chosen.

  • services.loadbalanced is set to true if your Kubernetes deployment supports automatic configuration of a load balancer (for example, AKS, EKS, and GKE).

If you are using SUSE Enterprise Storage, you must copy the Ceph admin secret to the metrics namespace:

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

Install Metrics with:

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

Monitor progress:

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

When all statuses show Ready, press CtrlC to exit and to view your release information.

6.6.3 Connecting Stratos Metrics

When Stratos Metrics is connected to Stratos, additional views are enabled that show metrics metadata that has been ingested into the Stratos Metrics Prometheus server.

To enable this, you must register and connect your Stratos Metrics instance 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. Next:

  1. Select Metrics from the Endpoint Type dropdown.

  2. Enter a memorable name for your environment in the Name field.

  3. Enter the Endpoint Address. Use the following to find the endpoint value.

    tux > kubectl get service susecf-metrics-metrics-nginx --namespace metrics
    • For Microsoft AKS, Amazon EKS, and Google GKE deployments which use a load balancer, the output will be similar to the following:

      NAME                           TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)         AGE
      susecf-metrics-metrics-nginx   LoadBalancer   10.0.202.180   52.170.253.229   443:30263/TCP   21h

      Preprend https:// to the public IP of the load balancer, and enter it into the Endpoint Address field. Using the values from the example above, https://52.170.253.229 is entered as the endpoint address.

    • For SUSE CaaS Platform deployments which do not use a load balancer, the output will be similar to the following:

      NAME                           TYPE       CLUSTER-IP       EXTERNAL-IP               PORT(S)         AGE
      susecf-metrics-metrics-nginx   NodePort   172.28.107.209   10.86.101.115,172.28.0.31 443:30685/TCP   21h

      Prepend https:// to the external IP of your node, followed by the nodePort, and enter it into the Endpoint Address field. Using the values from the example above, https://10.86.101.115:30685 is entered as the endpoint address.

  4. Check the Skip SSL validation for the endpoint checkbox if using self-signed certificates.

  5. Click Finish.

The view will refresh to show the new endpoint in the disconnected state. Next you will need to connect to this endpoint.

In the table of endpoints, click the overflow menu icon alongside the endpoint that you added above, then:

  1. Click on Connect in the dropdown menu.

  2. Enter the username for your Stratos Metrics instance. This will be the metrics.username defined in your stratos-metrics-values.yaml file.

  3. Enter the password for your Stratos Metrics instance. This will be the metrics.password defined in your stratos-metrics-values.yaml file.

  4. Click Connect.

Once connected, you should see that the name of your Metrics endpoint is a hyperlink and clicking on it should show basic metadata about the Stratos Metrics endpoint.

Metrics data and views should now be available in the Stratos UI, for example:

  • On the Instances tab for an Application, the table should show an additional Cell column to indicate which Diego Cell the instance is running on. This should be clickable to navigate to a Cell view showing Cell information and metrics.

    Cell Column on Application Instance Tab after Connecting Stratos Metrics
    Figure 6.9: Cell Column on Application Instance Tab after Connecting Stratos Metrics
  • On the view for an Application there should be a new Metrics tab that shows Application metrics.

    Application Metrics Tab after Connecting Stratos Metrics
    Figure 6.10: Application Metrics Tab after Connecting Stratos Metrics
  • On the Kubernetes views, views such as the Node view should show an additional Metrics tab with metric information.

    Node Metrics on the Stratos Kubernetes View
    Figure 6.11: Node Metrics on the Stratos Kubernetes View