2. Prerequisites

Pre-requisites

The following is a checklist of requirements, and additional configurations that will require modification of the default custom resource yaml.

Category	Requirements
Version	Kubernetes 1.22 and higher, linux x86 architecture. Support for OpenShift. Server platform can run on AKS, EKS, GKE, or any upstream compliant k8s, but IBM Turbo Support is not able to provide assistance.
Resources	Based on the total number of entities to be managed in your environment (VMs, Containers/Pods, Cloud Accounts, etc). See Sizing Table in Sizing Your Deployment.
Desired Targets	Enabled through Probe settings in Custom Resource yaml.
Access	Cluster admin, and kubectl CLI (optional mysql client for remote DB setup). Turbonomic Operator deployment yamls from github project
Network	Will create a NGINX LoadBalancer service, which will use an IP address or LB (external or internal) depending on the annotation. Default is Public IP/ELB. For details on ingress options and annotations, refer to NGINX Service Configuration Options or Platform Provided Ingress
Container Images	Private and public repos supported. Default is pulling from public Docker Hub Turbonomic repo. List of images to download is in Working with a Private Repo & Image Pull Secrets
Security Context	Components will need access to RW to PVs, and for some environments such as OpenShift, you will need to configure security context or supply fsgroup information to the deployment. See Deployment Steps - OCP Security Context for more information.
Storage	Dynamically provisioned PVs created through PVCs. Multizone/region clusters require volumeBindingMode = WaitForFirstConsumer. See Storage Class Requirements for PVC details and total storage required
Remote DB (recommended)	MariaDB v10.2. Version 10.5.16 is preferred. You can also use MySQL 5.7 with 8 Gb RAM, 4 vCore(s), 500 GB disk/file system space for tables. See Using a Database Server or Service. Using a containerized DB is not recommended because it does not provide transactional and performance guarantees.
Reporting options	Turbonomic offers 2 reporting options, that offer different features and scalability, with 2 different deployment scenarios. SaaS: designed for large environments, and more data analytics capabilities – see Data Cloud Reporting. Basic: environments of less than 10K VMs managed.
PV Backup	Customer will provide a PV backup and restore strategy. Key component PVs to manage are: consul, auth, topology-processor, and db components (MariaDB and timescaledb if applicable).

Next step: See Sizing Your Deployment