When using the Mission Control SaaS the agent based approach is recommended for ingesting data, The agent is headless installation of mission-control that caches data locally in a postgres database and replicates it to the SaaS.

SaaS/Agent Deployment Architecture

The agent based approach has the following benefits:

• Least privilege, as the agent runs within your infrastructure there is no network access or credentials required to be configured on the SaaS.
• CRD Based Configuration of health checks and scrape configs co-located with your IaC/App without the need to push any config to the SaaS.
• Local Playbook Execution on agents, reusing existing secrets or IAM roles.

See Installation for other deployment models including Self Hosted and Fully Hosted options

---

Signup

1. Goto accounts.flanksource.com/sign-up to signup

   

2. Choose an organisation name and logo
   

3. Invite your team members

   note

   Organization details and members can be changed by going to accounts.flanksource.com/organization
   or Clicking on Manage Organization when logged in

Agent Installation

Next an agent needs to deployed to scrape resources and execute playbooks:

Prerequisites

To install and run the Mission Control agent you need to have the following prerequisites:

• Kubernetes v1.27+ and Helm v3
• 1 - 2 CPU cores and 4GB of Memory
• Persistent Volumes with 10GB+ of storage or an external postgres database like RDS.

The recommended way of installing an agent is generating the Helm/Flux install script on the UI:

UI

1. Navigate to app.flanksource.com/settings/agents

   

2. Click on the

   button, and enter in the dialog:
   • clusterName
   • Toggle Kubernetes to automatically scrape the cluster the agent is installed in, you can skip this step and perform it later by installing the chart

3. Click Next

   You should see an installation script generated for Flux or Helm CLI

   

Helm

helm repo add flanksource https://flanksource.github.io/charts 
helm repo update
helm install mission-control-agent flanksource/mission-control-agent \
 --set clusterName=<Unique name for this agent> \
 --set upstream.agent=YOUR_LOCAL_NAME \
 --set upstream.username=token \
 --set upstream.password= \
 --set upstream.host= \
 -n mission-control --create-namespace \
 --wait 

values.yaml

• image:
  • repository: string
  • pullPolicy: string
  • tag: string
• serviceAccount:
  • annotations:
• upstream:
  • createSecret: boolean
  • host: string
  • username: string
  • password: string
  • agentName: string
  • secretName: string
• resources:
  • requests:
    • cpu: string
    • memory: string
  • limits:
    • memory: string
    • cpu: string
• db:
  • create: boolean
  • conf:
  • secretKeyRef:
    • name: string
    • key: string
  • jwtSecretKeyRef:
    • name: string
    • key: string
  • storageClass: string
  • storage: string
  • shmVolume: string
  • resources:
    • requests:
      • memory: string
• canary-checker:
  • image:
    • type: string
  • db:
    • runMigrations: boolean
    • external:
      • enabled: boolean
      • create: boolean
      • secretKeyRef:
        • name: string
        • key: string
  • flanksource-ui:
    • enabled: boolean
• config-db:
  • disablePostgrest: boolean
  • db:
    • runMigrations: boolean
    • embedded:
      • persist: boolean
    • external:
      • enabled: boolean
      • secretKeyRef:
        • name: string
        • key: string

Flux

apiVersion: v1
kind: Namespace
metadata:
name: mission-control
---
apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmRepository
metadata:
name: flanksource
namespace: mission-control
spec:
interval: 5m0s
url: https://flanksource.github.io/charts
---
apiVersion:  helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: mission-control-agent
namespace: mission-control
spec:
chart:
spec:
chart: mission-control-agent
sourceRef:
  kind: HelmRepository
  name: flanksource
  namespace: mission-control
interval: 1m
values:
    clusterName: <Unique name for this agent>
    upstream.agent: YOUR_LOCAL_NAME
    upstream.username: token
    upstream.password: 
    upstream.host: 

values.yaml

• image:
  • repository: string
  • pullPolicy: string
  • tag: string
• serviceAccount:
  • annotations:
• upstream:
  • createSecret: boolean
  • host: string
  • username: string
  • password: string
  • agentName: string
  • secretName: string
• resources:
  • requests:
    • cpu: string
    • memory: string
  • limits:
    • memory: string
    • cpu: string
• db:
  • create: boolean
  • conf:
  • secretKeyRef:
    • name: string
    • key: string
  • jwtSecretKeyRef:
    • name: string
    • key: string
  • storageClass: string
  • storage: string
  • shmVolume: string
  • resources:
    • requests:
      • memory: string
• canary-checker:
  • image:
    • type: string
  • db:
    • runMigrations: boolean
    • external:
      • enabled: boolean
      • create: boolean
      • secretKeyRef:
        • name: string
        • key: string
  • flanksource-ui:
    • enabled: boolean
• config-db:
  • disablePostgrest: boolean
  • db:
    • runMigrations: boolean
    • embedded:
      • persist: boolean
    • external:
      • enabled: boolean
      • secretKeyRef:
        • name: string
        • key: string

Encrypting the Token

We recommend that the upstream token be stored and encrypted using sops or similar

1. Create a new secret called mission-control-upstream:

     apiVersion: v1
     kind: Secret
     metadata:
       name: mission-control-upstream
     stringData:
       UPSTREAM_HOST: ""
       UPSTREAM_USER: token
       UPSTREAM_PASSWORD: ""
       AGENT_NAME: "YOUR_LOCAL_NAME"
   

2. Update the chart values:

   upstream:
     createSecret: false
     secretName: mission-control-upstream
   

Registry