Infrastructure and Agents User Guide

Connect Kubernetes clusters, Docker VM targets, multi-cloud resources, and outbound-only Inwire agents to the control plane.

Who This Guide Is For

• Platform engineers
• Cloud engineers
• MLOps operators

Where To Go

Page	Use It For
/infrastructure	Infrastructure overview.
/infrastructure/clusters	Connected cluster inventory.
/modelops/deployments/create	Deploy to connected targets.
/modelops/gitops	GitOps status and configuration.

Core Concepts

Concept	Meaning
Inwire Agent	An outbound-only Kubernetes controller that connects private clusters to Inwire.
Docker Agent	A lightweight VM agent for Docker-based deployment and fast iteration.
Cluster	A Kubernetes target such as EKS, GKE, AKS, on-prem, OpenShift, or K3s.
VM target	A Docker-capable machine registered for Docker deployments.
GitOps	Repository-driven manifest deployment and ArgoCD synchronization.

Common Workflows

Connect a Kubernetes cluster

1. Open Infrastructure -> Clusters.
2. Create or copy the cluster registration token.
3. Install the Inwire Agent with Helm.
4. Wait for heartbeat and capability discovery.
5. Confirm GPU and node pool telemetry.
6. Use the cluster in ModelOps deployments.

Use Docker targets

1. Install the Docker agent on a VM.
2. Confirm outbound connection to the control plane.
3. Verify Docker and GPU availability.
4. Select the VM in the Docker deployment path.
5. Review Compose preview and deploy.

Best Practices

• Use outbound-only agent connectivity; avoid inbound cluster exposure.
• Keep agent tokens secret and rotate them if exposed.
• Validate GPU, storage, and node labels before production scheduling.
• Use namespace and RBAC boundaries for shared clusters.