DOCSEARCHbyAlgolia
Submit Docs

Flanksource Mission Control

website·Indexed 32 days ago

https://flanksource.com/docs

A source-open, Kubernetes-native Internal Developer Platform (IDP) designed to improve developer productivity and operational resilience. It features a micro-service architecture with capabilities for infrastructure inventory, audit and compliance reporting, identity and access consolidation, and health monitoring via Canary Checker.

Tokens
294.1K
Snippets
1.4K
Records
1.9K
Agent score
65%

What's inside Mission Control

  1. Overview of the Terraform Scraper

    The Terraform scraper reads Terraform state files and creates configuration items from the resources defined in the state. This allows developers to track infrastructure as code (IaC) resources, monitor changes to managed infrastructure, detect state drift, map resource dependencies, and ensure compliance monitoring across multiple environments.

  2. Overview of Mission Control Views

    Views are dynamic, data-driven dashboards in Mission Control that aggregate and visualize data from multiple sources. They function by collecting data into an in-memory SQLite database, allowing users to use SQL for filtering, joining, and aggregating observability data. Key capabilities include support for templating variables, intelligent result caching, data transformation via expressions, and the ability to embed views within config item pages or assemble them into larger pages using sections.

  3. Overview of Kubernetes connections in Mission Control

    Kubernetes connections enable integration with clusters for health checks, configuration scraping (via the Kubernetes Config Scraper), executing commands in pods (via Pod Exec Action), and general playbook automation. To establish a connection, you must provide exactly one of the following connection types: kubeconfig, eks, gke, or cnrm.

  4. Overview of Identity & Access consolidation in Mission Control

    Mission Control consolidates identity data from disparate sources into a unified catalog to track who has access to what across an entire infrastructure. By mapping access to specific applications via the Application CRD, organizations can identify unauthorized access, enforce least-privilege principles, and meet regulatory requirements such as SOC 2, HIPAA, and ISO 27001.

  5. Overview of the Mission Control Catalog

    The Mission Control Catalog is a centralized repository powered by config-db that automatically discovers, transforms, and tracks infrastructure, applications, and configuration across multiple environments. It provides automatic discovery of resources (e.g., Kubernetes, AWS, Git, SQL), tracks changes via diffs or events to improve MTTR, aggregates security and performance insights, and maps dependencies between resources.

  6. Overview of the GitOps Action

    The GitOps action automates the process of creating commits and pushing changes to a Git repository. It is primarily used to provide a GUI for managing Infrastructure as Code (IaC) while maintaining a Git-based workflow. It features native support for Flux and Kustomization, allowing it to automatically identify the correct Git repository and file paths using originAnnotations from a Kustomization CRD.

  7. Overview of Mission Control Kustomize Integration

    Mission Control integrates with Kustomize and Flux GitOps to simplify configuration management. It allows users to automate Kustomize operations—such as creating resources or modifying existing ones—via playbooks that commit changes back to Git repositories and generate pull requests for review.

  8. Overview of Clickhouse Scraper capabilities

    Mission Control integrates with Clickhouse to scrape configuration data from various sources using Clickhouse's SQL engine and table functions. Supported data sources include:

    • Clickhouse Database: Direct connection to tables and materialized views.
    • AWS S3: Query objects using the s3() function.
    • Google Cloud Storage: Query objects using the gcs() function.
    • Azure Blob Storage: Query blobs using azureBlobStorage().
    • HTTP/HTTPS URLs: Query files from any HTTP endpoint using the url() function.
    • HDFS: Query files from Hadoop clusters using the hdfs() function.
    • MySQL: Query remote MySQL databases using the mysql() function.
    • PostgreSQL: Query remote PostgreSQL databases using the postgresql() function.

    Supported file formats for processing include CSV, JSON, Parquet, and Iceberg.

  9. Overview of Mission Control SSO and Identity Management

    Mission Control utilizes Ory Kratos for identity management. While email/password login is the default authentication flow, any OIDC provider supported by Kratos can be integrated for Single Sign On (SSO).

  10. Overview of Mission Control integration capabilities

    Mission Control integrates with various platforms to provide four primary capabilities:

    • Health: Monitor service availability and performance.
    • Scraper: Import configuration data into the catalog.
    • Notifications: Send alerts to messaging platforms.
    • Playbook: Execute automated actions and workflows.

  11. Overview of Prometheus monitoring system

    Prometheus is an open-source monitoring tool designed for systems and services, particularly containerized environments. It collects metric data at customizable intervals and stores it in a custom format optimized for disk and memory efficiency. It supports scaling through built-in sharding and federation features.

  12. Overview of Flux Topology monitoring

    The Flux topology provides a visual representation of Flux-based GitOps infrastructure. It monitors and maps relationships between the following components:

    • Controllers: Flux system pods within the flux-system namespace.
    • Releases: HelmRelease resources, including status, health, version, and related pod connections.
    • Kustomizations: Kustomization resources, including deployment status, health metrics, and associated pods.
    • Repositories: Helm, OCI, and Git repositories, tracking sync states, health, and error conditions.

    Key capabilities include real-time visibility into workflows, the ability to silence notifications at the Kustomization or HelmRelease level, and comprehensive property tracking for troubleshooting.