Reference: Step-wise platform deployment

Note:

The process that is described here is applicable only to the OVA deployment model.

After you install the Turbonomic VM that will host the platform, you can install the platform components, as follows:

(Optional) Configure Single Sign-On Authentication (SSO) for this installation.

If you plan to use SSO to authenticate your Turbonomic users, edit the charts_v1alpha1_xl_cr.yaml file before you complete the installation, or edit it later and restart the affected components. For more information, see Single Sign-On Authentication.
Deploy Turbonomic Kubernetes nodes.

When you deploy Turbonomic on Kubernetes, you deploy one Kubernetes node as a VM that hosts pods to run the Turbonomic components. The script to deploy and initialize the Kubernetes node also deploys the Kubernetes pods that make up the Turbonomic application.

Start a secure session (SSH) on your Turbonomic VM as the turbo user and complete the following steps:
1. Initialize the Kubernetes node and deploy the pods.
```
sudo /opt/local/bin/t8cInstall.sh
```
  The script takes up to 20 minutes to complete.
  Note:
  You can specify the hostname for the Turbonomic deployment. By default, the Turbonomic platform deploys to a host named node1. To specify a different hostname, run the script with the -h flag as follows:
```
sudo /opt/local/bin/t8cInstall.sh -h <MyHostName>
```
  Where <MyHostName>:
  - Consists of lowercase alphanumeric characters, periods (.) or hyphens (-)
  - Begins and ends with an alphanumeric character.
  After you change the hostname, you must restart the VM for the name change to take effect.
2. Verify that the deployment succeeded.
  
  At the end of the script output, in the summary section, verify that no errors are reported. If any errors are reported, contact Turbonomic Support.
3. Verify that Turbonomic installed correctly.
```
kubectl get pods -n turbonomic
```
  After all pods start, the READY column shows 1/1, 2/2, and so on. The STATUS column for each pod shows Running.
  
  The output is similar to the following example:
```
NAME                                         READY   STATUS    RESTARTS 
action-orchestrator-b6454c9c8-mfl85          1/1     Running   0         
api-7887c66f4b-shndq                         1/1     Running   0         
auth-5b86976bc8-vxwz4                        1/1     Running   0         
clustermgr-85548678d9-r5wb8                  1/1     Running   0         
consul-7f684d8cb8-6r677                      1/1     Running   0         
cost-5f46dd66c4-6d6cb                        1/1     Running   0          
extractor-5f41dd61c4-4d6lq                   1/1     Running   0        
group-5bfdfbc6f8-96bsp                       1/1     Running   0         
history-5fc7fbc855-6zslq                     1/1     Running   0         
kafka-74cc77db94-dfrbl                       1/1     Running   0         
kubeturbo-785945b66c-ltpjg                   1/1     Running   0 
market-5f54699447-z4wkm                      1/1     Running   0         
mediation-actionscript-57b4fc6df-4lzfv       1/1     Running   0         
mediation-appdynamics-6d65f8766f-kb44l       1/1     Running   0         
mediation-hpe3par-d7c475c4c-v8ftc            1/1     Running   0         
mediation-hyperv-6bd8c94df5-4dbzx            1/1     Running   0         
mediation-netapp-7f8fc955d9-4kkdl            1/1     Running   0         
mediation-oneview-7dbd7b54cf-7rfqp           1/1     Running   0         
mediation-pure-58c4bd8cd9-8n256              1/1     Running   0         
mediation-ucs-6f4bb9889-9rnqk                1/1     Running   0         
mediation-vcenter-5bc4f5fbd4-nzm4j           1/1     Running   0         
mediation-vcenterbrowsing-5c5987f66c-bfjq4   1/1     Running   0         
mediation-vmax-6c59969b89-28t9j              1/1     Running   0         
mediation-vmm-9c4878cf9-rfxnl                1/1     Running   0         
nginx-5b775f498-sm2mm                        1/1     Running   0         
plan-orchestrator-6dffc4c9b6-p5t5n           1/1     Running   0  
prometheus-mysql-exporter-5574d587c6-vnqx9   1/1     Running   0 
prometheus-server-64f6954bbf-xhvbb           2/2     Running   0  
reporting-b44fbdfb4-8fjv5                    1/1     Running   0         
repository-6d555bb4bf-fxldh                  1/1     Running   0         
rsyslog-fd694878c-5tb2c                      1/1     Running   0         
t8c-operator-558bcc758d-5h8mp                1/1     Running   0         
topology-processor-b646b786b-9skp7           1/1     Running   0         
zookeeper-5f65b5bf69-nnmbt                   1/1     Running   0         
              
```
4. Synchronize the system clock.
  
  To ensure the correct display of data, and to support Single Sign-On (SSO) authentication, you need to synchronize the system clock. For more information, see Synchronizing Time and Single Sign-On Authentication.
5. Verify that the Load Balancer installed correctly.
```
kubectl get services -n turbonomic | grep LoadBalancer
```
  The output is similar to the following example:
```
nginx  LoadBalancer   10.10.10.10   10.10.10.11  443:32669/TCP,80:32716/TCP  17h
```
6. Configure mediation.
  
  The installation script automatically enables a default set of mediation probes. After installation completes, you can change the set of enabled mediation probes (see Enabling and Disabling Probe Components).
  
  For Turbonomic to manage your IT environment, it must attach to targets in your environment so it can perform discovery and run actions. The combination of the processes of discovery and action execution is mediation. This release of Turbonomic supports mediation through the following targets.
  - Applications and Databases
    - Apache Tomcat 7.x, 8.x, or 8.5.x
    - Cisco AppDynamics 4.1+
    - Datadog
    - Dynatrace 1.1+
    - IBM WebSphere Application Server 8.5+
    - Instana release-242 or later
    - JBoss Application Server 6.3+
    - JVM 6.0+
    - SQL Server 2012, 2014, 2016, 2017, 2019, or 2022
    - MySQL 8.0
    - New Relic
    - Oracle 19c or 21c
    - Oracle WebLogic 12c
  - Container Platform
    - Kubernetes 1.27 up to the latest supported GA version, including (but not limited to) Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE), IBM Cloud Kubernetes Service (IKS), and Rancher
    - Red Hat supported GA versions of Red Hat OpenShift 4.1x, including (but not limited to) Red Hat OpenShift Kubernetes Service (ROKS), Red Hat OpenShift on AWS (ROSA), Red Hat OpenShift on Azure (ARO), and Red Hat OpenShift on Google
  - Custom
    - Data Ingestion Framework
  - Fabric and Network
    - Cisco UCS Manager 3.1+
    - HPE OneView 3.00.04
  - Guest OS Processes
    - SNMP
    - WMI: Windows 7, 8, 8.1, 10, 2008 R2, 2012, 2012 R2, 2016, or 2019
  - Hyperconverged
    - Cisco HyperFlex 3.5
    - Nutanix Community Edition
    - VMware vSAN
  - Hypervisors
    - IBM PowerVM
      - HMC 10: Power8, Power9, or Power10
      - HMC 9: Power8 or Power9 only; Power7 LPARs and Systems are ignored.
    - Microsoft Hyper-V 2012 R2, 2016, 2019, or 2022
    - VMware vCenter 7.0 or 8.0
  - IT Management
    - Flexera
      - Flexera One SaaS
      - FlexNet Manager Suite 2023 R2 or above
    - IBM Apptio
    - ServiceNow
      
      Certified for ServiceNow versions:
      - Utah
      - Vancouver
      - Washington DC
  - Observability
    - Prometheus
  - Orchestrator
    - Action Script
  - Private Cloud
    - VMM for Microsoft System Center 2012 R2, System Center 2016, System Center 2019, or System Center 2022
  - Public Cloud
    - Amazon Web Services (AWS)
    - AWS Billing
    - Azure Service Principal
    - Azure Billing
    - Microsoft Enterprise Agreement
    - Google Cloud
    - Google Cloud Billing
  - Storage
    - EMC ScaleIO 2.x or 3.x
    - EMC VMAX using SMI-S 8.1+
    - EMC VPLEX Local Architecture with 1:1 mapping of virtual volumes and LUNs
    - EMC XtremIO XMS 4.0+
    - HPE 3PAR InForm OS 3.2.2+, 3PAR SMI-S, 3PAR WSAPI
    - IBM FlashSystem running on Spectrum Virtualize 8.3.1.2 or later (8.4.2.0 or later recommended)
    - NetApp Cluster Mode using ONTAP 8.0+ (excluding AFF and SolidFire)
    - Pure Storage F-series and M-series arrays running Purity 5.3.6 and 6.4.4 (Pure API 1.6)
  - Virtual Desktop Infrastructure
    - Horizon 7.0 or higher
  For more information, see Target Configuration.
Important:
Wait until all the platform components start, are running, and are fully ready before your first log in. If you try to add a license or add a target to the platform before the components are all ready, the platform can fail to initialize correctly. After the components start, in your web browser, type the static IP address of your Turbonomic VM. Your browser redirects the login page for Turbonomic users.
Log in to the Turbonomic user interface using the server address and import your license key.

For more information, see this topic.
Create other user accounts with various roles. For more information about user accounts and roles, see this topic.

Note:
For security reasons, you can create a different account with an Administrator role to serve as the main administrator of your Turbonomic installation, and then delete the default administrator account. You must always have at least one user account with administrator privileges.