Skip to main content
RubixKube uses an environment-first model. This page helps you navigate how different environment types appear and behave in the product.

​
Environment Types in RubixKube

Environment typeTypical data shapePrimary guide
KubernetesCluster, node, namespace, pod signalsManaging Clusters (Kubernetes)
AWSAccount and regional cloud service signalsAWS Quick Start
GCPProject and regional cloud service signalsGCP Quick Start
VMSingle-host system and process signalsVM Quick Start

​
Terminology Rules

  • Use environment for generic product usage.
  • Use cluster only for Kubernetes-specific topics.
  • API compatibility terms like cluster_id may still appear in logs or payloads.

​
Common Operations

  • Confirm environment connection status.
  • Review incoming insights and infrastructure snapshots.
  • Validate observer credentials/permissions for each environment.
  • Use guided troubleshooting when data stops flowing.