Getting Started
This tutorial guides you through setting up and configuring a self-hosted Mission Control environment.
To install and run Mission Control you need the following:
- Kubernetes 1.26+ with an Ingress Controller
- cert-manager.io or an existing TLS secret for ingress
- 1 - 2 CPUs and 6-8GB of Memory (2-4GB if using an external DB)
- Persistent Volumes with 20GB+ of storage or an external postgres database
- (Optional) prometheus operator
- (Optional) SMTP Server (For sending notifications and invites)
-
Choose a routable
DOMAIN
for Mission ControlSee Ingress for more options on configuring the ingress including generating certs with cert-manager
See Local Testing for testing using a kind or minikube without a routable domain
-
Install Mission Control
tipIf you are installing on EKS and plan to scrape AWS resources use the method described in EKS instead
See values.yaml- Helm
- Flux
helm repo add flanksource https://flanksource.github.io/charts
helm repo update
helm install mission-control flanksource/mission-control \
--set global.ui.host=DOMAIN \
-n mission-control --create-namespace \
--waitapiVersion: v1
kind: Namespace
metadata:
name: mission-control
---
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
name: flanksource
namespace: mission-control
spec:
interval: 5m0s
url: https://flanksource.github.io/charts
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: mission-control
namespace: mission-control
spec:
chart:
spec:
chart: mission-control
sourceRef:
kind: HelmRepository
name: flanksource
namespace: mission-control
interval: 1m
values:
global.ui.host: DOMAIN -
Login @ https://DOMAIN/
The default username is
admin@local
and the password can be retrieved with:kubectl get secret mission-control-admin-password \
-n mission-control \
--template='{{.data.password | base64decode}}'
Optional Steps
3Configure Email (SMTP)An SMTP server is required for sending notifications, approvals, user invites and password resets.
The format of connection_uri
is smtp://hostname:port
values.yamlkratos:
kratos:
config:
courier:
smtp:
connection_uri: # smtp://localhost:25
from_address: noreply@
from_name: Mission Control
# These headers will be passed in the SMTP conversation
# e.g. when using the AWS SES SMTP interface for cross-account sending.
headers: {}
# Identifier used in the SMTP HELO/EHLO command.
# Some SMTP relays require a unique identifier.
local_name:
See also HTTP Webhooks for sending emails.
See SSO
See Database to configure an external database such as AWS RDS or Google Cloud SQL, or to optimize the bundled PostgreSQL settings.