Reference: Image listing

Turbonomic images are located at https://icr.io/cpopen/turbonomic, except for the operators which are located at https://icr.io/cpopen.

Note:

Starting with Turbonomic version 8.7.5, IBM Container Registry is used for all Turbonomic images for online upgrades and installations. Ensure that you have access to https://*.icr.io before continuing.

All of the required Turbonomic application images are listed in the following table. The total size of the required images is approximately 12GB. Adding additional components, such as probes or the secure client, increases the total size. Pull the image with the required tag, which is the version to deploy.

Image name Component type Required Comment
action-orchestrator Server Required Core (default) component
api Server Required Core (default) component
auth Server Required Core (default) component
clustermgr Server Required Core (default) component
consul Server Required Core (default) component
cost Server Required Core (default) component
group Server Required Core (default) component
history Server Required Core (default) component
kafka Server Required Core (default) component
kube-state-metrics Server Required Used by prometheus-kube-state-metrics, which is a core component
market Server Required Core (default) component
metadata Server Required Used by metadata, which is a core component
nginx Server Required Core (default) component
plan-orchestrator Server Required Core (default) component
prometheus Server Required Used by prometheus-server, which is a core component
prometheus-config-manager Server Required Used by prometheus-server, which is a core component
prometheus-kafka-adapter Server Required Used by prometheus-server, which is a core component
redis Server Required Used by Suspend, which is a core component
repository Server Required Core (default) component
rsyslog Server Required Core (default) component
server-power-modeler Server Required Core (default) component
suspend Server Required Core (default) component
sustainability Server Optional Enabled by default; used to calculate energy usage and carbon footprint of public cloud VMs
t8c-operator Server Required

See Turbonomic Updates and Operator Version
topology-processor Server Required Core (default) component
ui Server Required Core (default) component
zookeeper Server Required Core (default) component, used by Kafka
db Server Optional Used for containerized DB
kinesis-kafka-connect Server Optional Used by the Telemetry component
telemetry-scrubber Server Optional Used by Prometheus-server when Telemetry is enabled
extractor Embedded Reporting Optional Used for embedded reporting, SaaS Reporting, and Telemetry
grafana Embedded Reporting Optional Used for embedded reporting
timescaledb Embedded Reporting Optional

kubeturbo Probe (kubeturbo) Optional Used to support all Kubernetes related targets
kubeturbo-operator Probe (kubeturbo) Optional  
cpufreqgetter Probe (kubeturbo) Optional  
mediation-actionscript Probe Optional  
mediation-actionstream-kafka Probe Optional  
mediation-appdynamics Probe Optional  
mediation-aws Probe Optional  
mediation-awscloudbilling Probe Optional  
mediation-awscost Probe Optional  
mediation-azure Probe Optional  
mediation-azurebilling Probe Optional  
mediation-azurecost Probe Optional

mediation-azureea Probe Optional  
mediation-azureinfra Probe Optional  
mediation-azurepricing Probe Optional  
mediation-azuresp Probe Optional  
mediation-azurevolumes Probe Optional  
mediation-datadog Probe Optional  
mediation-dynatrace Probe Optional  
mediation-flexera Probe Optional  
mediation-gcpbilling Probe Optional  
mediation-gcpcost Probe Optional  
mediation-gcpinfra Probe Optional  
mediation-gcpproject Probe Optional  
mediation-gcpsa Probe Optional  
mediation-horizon Probe Optional  
mediation-hpe3par Probe Optional  
mediation-hyperflex Probe Optional  
mediation-hyperv Probe Optional  
mediation-ibmstorage-flashsystem Probe Optional  
mediation-instana Probe Optional  
mediation-jboss Probe Optional  
mediation-jvm Probe Optional  
mediation-mssql Probe Optional  
mediation-netapp Probe Optional  
mediation-newrelic Probe Optional  
mediation-nutanix Probe Optional  
mediation-oneview Probe Optional  
mediation-oracle Probe Optional  
mediation-powervm Probe Optional  
mediation-pure Probe Optional  
mediation-scaleio Probe Optional  
mediation-servicenow Probe Optional  
mediation-snmp Probe Optional  
mediation-tomcat Probe Optional  
mediation-ucs Probe Optional  
mediation-udt Probe Optional Enabled by default; used for the creation and discovery of application map entities
mediation-vcenter Probe Optional  
mediation-vcenterbrowsing Probe Optional  
mediation-vmax Probe Optional  
mediation-vmm Probe Optional  
mediation-vplex Probe Optional  
mediation-webhook Probe Optional  
mediation-weblogic Probe Optional  
mediation-websphere Probe Optional  
mediation-wmi Probe Optional  
mediation-xtremio Probe Optional  
prometurbo Probe Optional  
prometurbo-operator Probe Optional  
prometheus-server Probe Optional  
turbodif Probe Optional  
winrm-proxy Probe Optional  
hydra Secure client Optional  
kibitzer Secure client Optional Used to help in retrieving debug information for components such as history
rsyslog-courier Secure client Optional  
skupper-config-sync Secure client Optional  
skupper-router Secure client Optional  
skupper-service-controller Secure client Optional  
skupper-site-controller Secure client Optional  
t8c-client-operator Secure client Optional  
t8c-client-operator-bundle Secure client Optional  
t8c-client-operator-catalog Secure client Optional  
tsc-site-resources Secure client Optional  
Note:

  • Required server images are the minimal images that are needed to run the Turbonomic Server.

  • Reporting requires postgresql and timescale db, which are pulled from other repositories. See this chart for image details.

  • Kubeturbo, which should be deployed separately, provides robust container platform monitoring and management, including self-optimization of Turbonomic. For more information, see this topic.

  • If you want a copy of a sample deployment yaml file you will need access to GitHub to copy or clone the t8c-install project.