Skip to main content

Playbooks

Self-service playbooks empower teams to manage their Kubernetes resources efficiently:

  • Reduced operational overhead: Teams can perform common tasks without DevOps intervention
  • Standardized operations: Ensure consistent execution of tasks across clusters
  • Faster incident response: Enable developers to troubleshoot and resolve issues
  • Improved security: Controlled access to cluster operations through predefined playbooks
  • Better developer experience: User-friendly interface for complex Kubernetes operations Common use cases include:
  • Developers checking application logs and debugging issues
  • Teams scaling deployments during high traffic periods
  • Application owners updating container images for new releases
  • Project teams requesting access to namespaces
  • DevOps automating resource cleanup and management

The following playbooks are available for use:

Playbook
Pod
Deployment
Namespace
Cluster
Delete
Logs
Scale†
Update Resources
Update Image
Create Helm Chart
Create Deployment
Request Access
Create Namespace

Getting Started​

Prerequisites

To enable the Kubernetes integration you need:

  1. Install the mission-control-playbooks-kubernetes helm chart.

If you are using the SaaS, then this needs to be installed on the SaaS vCluster using kubectl

apiVersion:  helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: mission-control-playbooks-kubernetes
  namespace: mission-control
spec:
  chart:
    spec:
      chart: mission-control-playbooks-kubernetes
      sourceRef:
        kind: HelmRepository
        name: flanksource
        namespace: mission-control
  interval: 5m
values:
values.yaml
  • connections:
  • delete:
    • types[]:
  • global:

    Global values are values that can be accessed from any chart or subchart by exactly the same name.

      - Global values are values that can be accessed from any chart or subchart by exactly the same name.
    • playbooks:
      • cleanupFailedPods: boolean (default: true)
      • cordonNode: boolean (default: true)
      • createDeployment: boolean (default: true)
      • delete: boolean (default: true)
      • deployHelmChart: boolean (default: true)
      • drainNode: boolean (default: true)
      • enabled: boolean (default: true) - If this is set to false, no playbooks will be created
      • ignoreChanges: boolean (default: true)
      • logs: boolean (default: true)
      • podSnapshot: boolean
      • requestNamespaceAccess: boolean (default: true)
      • restart: boolean (default: true)
      • scale: boolean (default: true)
      • uncordonNode: boolean (default: true)
      • updateImage: boolean (default: true)
      • updateResources: boolean (default: true)
    • rbac:
    Note

    The playbooks chart only needs to be installed once, unlike the mission-control-kubernetes chart which is per cluster

    Customizing playbooks​

    Copy the playbook from here to your own repository.