Skip to main content
Version: v0.38 Stable

Integrate and automate

This section connects a cluster to the tools around it. Most integrations work in one of three ways, and the way decides what you install and where.

  • Reuse a tool on the control plane cluster. Tools such as cert-manager, External Secrets Operator, Istio, KubeVirt, and the metrics server run once on the control plane cluster. Each cluster's workloads use that installation. The cluster doesn't need its own copy.
  • Run a tool inside the cluster. Some tools run inside each cluster like any other workload, such as an inference serving stack.
  • Automate the cluster itself. GitOps and CI integrations create clusters from Git or from a pipeline. Some create short-lived clusters for tests.

To see the integrations for vCluster, vCluster Platform, and vMetal in one place, see all integrations.

Card tags show which worker node models a guide supports, Shared nodes or Private nodes. A Free or Enterprise tag means the integration needs a platform license at that tier. See Open Source vs Free tier for what the Free tier includes. Tags repeat what each guide states, so a missing tag means the guide doesn't state that requirement.

Bare metal and virtual machines​

Run virtual machines alongside the pods in a cluster. To provision bare metal servers or virtual machines as worker nodes, see vMetal.

Networking​

Add cluster workloads to a service mesh, and automate the network for the cluster control plane and private nodes.

AI and GPU workloads​

Schedule GPU workloads, serve models, and scale both on GPU and inference metrics.

GitOps, CI/CD, and automation​

Create and update clusters from Git or a CI pipeline, including short-lived clusters for tests and preview environments.

Identity, secrets, and policy​

Let workloads use cloud services through a cloud identity instead of long-lived credentials, bring in secrets from an external store, and issue TLS certificates.

Observability and fleet management​

Deliver the credential that a cluster's collectors use to reach Fleet Observability, make kubectl top work, and register clusters in Rancher.

Connectors and extensions​

To add sync logic, hooks, or controllers that no integration covers, write a custom plugin.