Skip to content
Slipwaydocs

Kubernetes

Deploy manifests, Helm releases and Kustomize overlays to any cluster.

At a glance

Section titled “At a glance”
Category Cloud & Kubernetes
Authentication kubeconfig, in-cluster service account, or cloud-provider federation
Provider id kubernetes

What it does

Section titled “What it does”
  • Rolling, blue/green and canary strategies
  • Drift detection (desired vs live)
  • Rollout health reads
  • Namespace-scoped RBAC

Set up

Section titled “Set up”
  1. Choose how the runner reaches the cluster: in-cluster (runner runs inside it), kubeconfig (stored as a secret), or cloud federation (EKS/GKE/AKS).
  2. Create a Role limited to the namespace and the resource kinds you deploy.
  3. Add the integration, then create an Infrastructure of kind kubernetes on each environment.
  4. Run Test infrastructure; Slipway performs a server-side dry-run apply.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: kubernetes
config:
  mode: in_cluster          # in_cluster | kubeconfig | cloud
  namespace: payments
  runner_pool: k8s-prod

Notes

Section titled “Notes”

Use one runner pool per cluster so credentials never leave the network that owns them.

Section titled “Related”