Skip to content

5. Deployment Validation and First Time Setup

Jump to bottom
Jason Shaw edited this page Jun 28, 2023 · 2 revisions

Deployment Validation and First Time Setup

Pods

Deployment will begin for all the Turbonomic pods. Depending on the environment, this may take some time to complete, anywhere from 5 to 20 minutes. Use kubectl get pods -n turbonomic -w or watch utility to check the status of the deployment. The following shows an example of the pods that you should see running, including a vCenter target. Your environment may have additional pods running that will reflect your targets or other integrations, such as Data Cloud, being enabled:

Launching the Turbonomic UI and License Configuration

If you are deploying in OpenShift or will leverage an existing Ingress Controller, refer to Platform Provided Ingress & OpenShift Routes to create Routes for UI and remote probe access. To get the IP address of the Turbonomic UI, you will need to identify the IP address of the nginx service.

$ kubectl get svc -n turbonomic | grep "LoadBalancer"

nginx LoadBalancer 10.100.14.25 {endpoint_name}.{yourCloud_domain} 443:30960/TCP,80:30860/TCP 38m

  • In a browser, point to this endpoint to see the first time login to create the "administrator" password:

  • The setup wizard will take you to importing the license key:

  • After you see “Success” with the correct license key, you can “Add Targets”:

  • Target types available are controlled through the Custom Resource file (refer back to Configure the Turbonomic Instance: Custom Resource). If you enabled the vCenter probe, you will see Hypervisor -> vCenter. Your list may vary.

  • If you wish to add other targets, modify the {path_to_modified_file}/deploy/crds/charts_v1alpha1_xl_cr.yaml file and reapply.

Deployment is now complete!

Next steps: Use Turbonomic! Review sections on Updating your Deployment and use Release Notes to determine if you need to update version for bugs or new features.

Clone this wiki locally