From 9ed43a15617189cc40572b995041342d9826f899 Mon Sep 17 00:00:00 2001 From: Aditya Thebe Date: Thu, 26 Dec 2024 11:12:52 +0545 Subject: [PATCH] chore: format and bump submodules --- .../docs/comparisons/blackbox-exporter.md | 1 + .../docs/comparisons/kuberhealthy.md | 1 + canary-checker/docs/concepts/performance.md | 1 + canary-checker/docs/helm.canary.md | 105 ++++++------ canary-checker/docs/reference/index.md | 2 - canary-checker/docs/scripting/jsonpath.md | 1 + mission-control-chart | 2 +- mission-control/blog/canary-checker-v1.1.0.md | 12 +- .../docs/guide/config-db/concepts/changes.md | 1 - .../guide/config-db/concepts/health_status.md | 1 - .../guide/config-db/concepts/transform.md | 1 - .../docs/guide/config-db/scrapers/_custom.md | 20 +-- .../docs/guide/config-db/scrapers/aws.md | 10 +- .../docs/guide/config-db/scrapers/azure.md | 12 +- .../docs/guide/playbooks/actions/index.md | 28 ++-- .../guide/playbooks/concepts/expression.md | 2 +- .../docs/guide/playbooks/webhooks.md | 1 - mission-control/docs/guide/topology/index.md | 1 - .../docs/guide/topology/lookups/exec.md | 8 +- .../docs/guide/topology/lookups/kubernetes.md | 20 +-- .../docs/guide/topology/lookups/prometheus.md | 8 +- .../docs/integrations/aws/getting-started.md | 27 +-- mission-control/docs/integrations/aws/iam.md | 155 +++++++++--------- .../docs/integrations/aws/index.md | 1 - .../docs/integrations/flux/catalog.md | 13 +- .../docs/integrations/flux/index.md | 2 - .../docs/integrations/flux/playbooks.md | 9 +- .../docs/integrations/flux/topology.md | 3 +- .../docs/integrations/kubernetes/index.md | 3 - .../docs/integrations/kubernetes/playbooks.md | 6 +- .../docs/reference/config-db/index.md | 1 - .../docs/reference/playbooks/index.md | 33 ++-- .../docs/reference/topology/_lookup.md | 20 +-- .../docs/reference/topology/properties.md | 14 +- modules/canary-checker | 2 +- modules/config-db | 2 +- modules/duty | 2 +- modules/mission-control | 2 +- modules/mission-control-chart | 2 +- modules/mission-control-registry | 2 +- 40 files changed, 251 insertions(+), 286 deletions(-) diff --git a/canary-checker/docs/comparisons/blackbox-exporter.md b/canary-checker/docs/comparisons/blackbox-exporter.md index 0ea1b2a..0ab6120 100644 --- a/canary-checker/docs/comparisons/blackbox-exporter.md +++ b/canary-checker/docs/comparisons/blackbox-exporter.md @@ -3,6 +3,7 @@ title: Blackbox Exporter sidebar_custom_props: icon: prometheus --- + # Canary-Checker vs Prometheus blackbox exporter [Prometheus Blackbox Exporter](https://github.com/prometheus/blackbox_exporter) is a prometheus exporter for probing HTTP, HTTPS, DNS, TCP, ICMP, and gRPC. diff --git a/canary-checker/docs/comparisons/kuberhealthy.md b/canary-checker/docs/comparisons/kuberhealthy.md index 64d2e5f..38fb8da 100644 --- a/canary-checker/docs/comparisons/kuberhealthy.md +++ b/canary-checker/docs/comparisons/kuberhealthy.md @@ -1,6 +1,7 @@ --- draft: true --- + ### Kuberhealthy https://github.com/kuberhealthy/kuberhealthy diff --git a/canary-checker/docs/concepts/performance.md b/canary-checker/docs/concepts/performance.md index 5b3ae0a..5137497 100644 --- a/canary-checker/docs/concepts/performance.md +++ b/canary-checker/docs/concepts/performance.md @@ -1,6 +1,7 @@ --- draft: true --- + ## Disable Check Status Aggregation jobs.AggregateCheckStatuses1h.disable=true diff --git a/canary-checker/docs/helm.canary.md b/canary-checker/docs/helm.canary.md index 21e7c33..5675839 100644 --- a/canary-checker/docs/helm.canary.md +++ b/canary-checker/docs/helm.canary.md @@ -5,81 +5,76 @@ sidebar_class_name: hidden-mission-control slug: /guide/canary-checker/helm --- - - import Schema from '@site/modules/canary-checker/chart/values.schema.json' - # Quick Start The recommended method for installing Canary Checker is using [helm](https://helm.sh/) 1. Install [canary-checker](https://github.com/flanksource/canary-checker) helm chart - + - :::info - Note the default installation of canary-checker uses an embedded postgres database and does not persist history, see: [Database](database) - ::: + :::info + Note the default installation of canary-checker uses an embedded postgres database and does not persist history, see: [Database](database) + ::: 1. Create a canary - ```bash - cat < -1. Check the results via the [CLI](./cli) + ```bash + cat < +1. Check the results via the [CLI](./cli) - - NAME INTERVAL STATUS LAST CHECK UPTIME 1H LATENCY 1H LAST TRANSITIONED - http-check 30 Passed 13s 18/18 (100.0%) 480ms 13s - + +NAME INTERVAL STATUS LAST CHECK UPTIME 1H LATENCY 1H LAST TRANSITIONED +http-check 30 Passed 13s 18/18 (100.0%) 480ms 13s + 1. Access the dashboard - You can access the web [dashboard](http://localhost:8080) by forwarding the port: - - -   - - - - + You can access the web [dashboard](http://localhost:8080) by forwarding the port: + +   + + - :::tip + :::tip - To deploy an ingress for the dashboard, update the `values.yaml`: + To deploy an ingress for the dashboard, update the `values.yaml`: - ```yaml - flanksource-ui: - enabled: true - ingress: - annotations: - kubernetes.io/tls-acme: 'true' - host: - tls: - - hosts: - - - secretName: ingress-tls - ``` + ```yaml + flanksource-ui: + enabled: true + ingress: + annotations: + kubernetes.io/tls-acme: 'true' + host: + tls: + - hosts: + - + secretName: ingress-tls + ``` - ::: +::: diff --git a/canary-checker/docs/reference/index.md b/canary-checker/docs/reference/index.md index 0d300e2..fa353e2 100644 --- a/canary-checker/docs/reference/index.md +++ b/canary-checker/docs/reference/index.md @@ -5,8 +5,6 @@ sidebar_custom_props: icon: codicon:pass --- - - import DocCardList from '@theme/DocCardList'; diff --git a/canary-checker/docs/scripting/jsonpath.md b/canary-checker/docs/scripting/jsonpath.md index 9b79ba7..c5f6c56 100644 --- a/canary-checker/docs/scripting/jsonpath.md +++ b/canary-checker/docs/scripting/jsonpath.md @@ -1,6 +1,7 @@ --- draft: true --- + Testing JSONPath expressions: ``` diff --git a/mission-control-chart b/mission-control-chart index b605f56..6e75633 160000 --- a/mission-control-chart +++ b/mission-control-chart @@ -1 +1 @@ -Subproject commit b605f56818d804f17a66875aebe46ab421de92dc +Subproject commit 6e756337145ca0b9227001964b71246c4d071df4 diff --git a/mission-control/blog/canary-checker-v1.1.0.md b/mission-control/blog/canary-checker-v1.1.0.md index 51ae8ff..a54bad6 100644 --- a/mission-control/blog/canary-checker-v1.1.0.md +++ b/mission-control/blog/canary-checker-v1.1.0.md @@ -6,15 +6,15 @@ tags: [release, canary-checker] hide_table_of_contents: false --- - + We are happy to announce the latest release of canary-checker, the highlight of which is Kubernetes resource checker that enables continuous testing of Crossplane, Helm, Flux and other K8s resources. ## Checks - ⛰️`kubernetes`, `kubernetesResource` - Added support for external `kubeconfig` - ⛰️ `kubernetesResource` - Improved the speed of deleting Kubernetes resources -- ⛰️ `http`, `prometheus` - Added OAuth and TLS Client options +- ⛰️ `http`, `prometheus` - Added OAuth and TLS Client options - ⛰️ `http` - Support templating `url` from env vars - ⛰️ `aws*` - Added support for assumeRole - 🐛 `webhook` - Fixed webhook handling and added 📚 example for githubstatus.com @@ -42,19 +42,13 @@ We are happy to announce the latest release of canary-checker, the highlight of - ⛰️ Added [`jq`](/reference/scripting/cel#jq) - ⛰️ Added support for custom delimiters using `# gotemplate: left-delim=$[[ right-delim=]]` - ## Breaking -- Removed `configDb` check, Use `catalog` (Config DB) instead +- Removed `configDb` check, Use `catalog` (Config DB) instead - Removed `ec2` check, Use `kubernetesResource` with Crossplane or ACK instead - ## New Contributors ❤️ - Big thanks to our contributors: [@nalshamaajc](https://github.com/nalshamaajc), [@bosunski](https://github.com/bosunski), [@DanielCastronovo](https://github.com/DanielCastronovo), [@dmorrowjc](https://github.com/dmorrowjc), [@RaymiiOrg](https://github.com/RaymiiOrg), [@fullykubed](https://github.com/fullykubed), [@krohrsb](https://github.com/krohrsb), [@sosheskaz](https://github.com/sosheskaz), [@PrestonCS](https://github.com/PrestonCS), [@miry](https://github.com/miry), [@oc-christopher-billett](https://github.com/oc-christopher-billett), [@LarsFronius](https://github.com/LarsFronius), [@christianshub](https://github.com/christianshub), [@EugeneBad](https://github.com/EugeneBad) - - - diff --git a/mission-control/docs/guide/config-db/concepts/changes.md b/mission-control/docs/guide/config-db/concepts/changes.md index f7ced02..d2406e9 100644 --- a/mission-control/docs/guide/config-db/concepts/changes.md +++ b/mission-control/docs/guide/config-db/concepts/changes.md @@ -2,7 +2,6 @@ title: Changes sidebar_custom_props: icon: octicon:diff-16 - --- When you save a config item to Config DB, it tracks its changes. These changes come from external sources like Kubernetes events or Azure activities. Alternatively, Mission Control can automatically detect changes by comparing the old config with the new one. diff --git a/mission-control/docs/guide/config-db/concepts/health_status.md b/mission-control/docs/guide/config-db/concepts/health_status.md index 032cba9..71037c9 100644 --- a/mission-control/docs/guide/config-db/concepts/health_status.md +++ b/mission-control/docs/guide/config-db/concepts/health_status.md @@ -2,7 +2,6 @@ title: Health & Status sidebar_custom_props: icon: mdi-light:heart - --- Each config item has attributes used to determine the health and status of an item. diff --git a/mission-control/docs/guide/config-db/concepts/transform.md b/mission-control/docs/guide/config-db/concepts/transform.md index d61303f..8c106c4 100644 --- a/mission-control/docs/guide/config-db/concepts/transform.md +++ b/mission-control/docs/guide/config-db/concepts/transform.md @@ -2,7 +2,6 @@ title: Transformation sidebar_custom_props: icon: hugeicons:code - --- Transformations allow you to modify scraped config items before they are saved, common use cases include: diff --git a/mission-control/docs/guide/config-db/scrapers/_custom.md b/mission-control/docs/guide/config-db/scrapers/_custom.md index f85810e..ade822b 100644 --- a/mission-control/docs/guide/config-db/scrapers/_custom.md +++ b/mission-control/docs/guide/config-db/scrapers/_custom.md @@ -2,18 +2,18 @@ Custom scrapers require defining the `id`, `type`, and `class` for each scraped item. For example, when scraping a file containing a JSON array, where each array element represents a config item, you need to specify the `id`, `type`, and config `class` for these items. Achieve this by utilizing mappings in your custom scraper configuration. -| Field | Description | Scheme | Required | -| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | -------- | +| Field | Description | Scheme | Required | +| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | -------- | | `items` | A path pointing to an array, each item is created as a separate config item, all other JSONPath is evaluated from the new items root | _`JSONPath`_ | `true` | -| `id` | ID for the config item | _`JSONPath`_ | `true` | -| `type` | Type for the config item | _`JSONPath`_ | `true` | -| `class` | Class for the config item. _(Defaults to `type`)_ | _`JSONPath`_ | | -| `name` | Name for the config item | _`JSONPath`_ | | -| `format` | Format of the config source. Defaults to `json` | `json`, `xml` or `properties` See [Formats](#formats) | | -| `createFields` | Fields to use to determine the items created date, if not specified or the field is not found, defaults to scrape time | _`[]JSONPath`_ | | +| `id` | ID for the config item | _`JSONPath`_ | `true` | +| `type` | Type for the config item | _`JSONPath`_ | `true` | +| `class` | Class for the config item. _(Defaults to `type`)_ | _`JSONPath`_ | | +| `name` | Name for the config item | _`JSONPath`_ | | +| `format` | Format of the config source. Defaults to `json` | `json`, `xml` or `properties` See [Formats](#formats) | | +| `createFields` | Fields to use to determine the items created date, if not specified or the field is not found, defaults to scrape time | _`[]JSONPath`_ | | | `deleteFields` | Fields to use to determine when an item was deleted if not specified or the field is not found, defaults to scrape time of when the item is no longer detected | _`[]JSONPath`_ | | -| `timestampFormat` | Timestamp format of `createFields` and `deleteFields`. _(Default 2006-01-02T15:04:05Z07:00)_ | [`time.Format`](https://golang.org/pkg/time/#Time.Format) | | -| `full` | Scrape result includes the full metadata of a config, including possible changes, See [Change Extraction](#change-extraction) | `bool` | | +| `timestampFormat` | Timestamp format of `createFields` and `deleteFields`. _(Default 2006-01-02T15:04:05Z07:00)_ | [`time.Format`](https://golang.org/pkg/time/#Time.Format) | | +| `full` | Scrape result includes the full metadata of a config, including possible changes, See [Change Extraction](#change-extraction) | `bool` | | ## Formats diff --git a/mission-control/docs/guide/config-db/scrapers/aws.md b/mission-control/docs/guide/config-db/scrapers/aws.md index 1c73011..6ef98ad 100644 --- a/mission-control/docs/guide/config-db/scrapers/aws.md +++ b/mission-control/docs/guide/config-db/scrapers/aws.md @@ -19,11 +19,11 @@ The registry has an [AWS](/registry/aws) Helm chart that provides a pre-configur ``` -| Field | Description | Scheme | Required | -| ----------- | ---------------------------------------------------------------------------- | -------------------------------------------- | -------- | -| `schedule` | Specify the interval to scrape in cron format. Defaults to every 60 minutes. | [Cron](/reference/types#cron) | | +| Field | Description | Scheme | Required | +| ----------- | ---------------------------------------------------------------------------- | -------------------------------------------------- | -------- | +| `schedule` | Specify the interval to scrape in cron format. Defaults to every 60 minutes. | [Cron](/reference/types#cron) | | | `retention` | Settings for retaining changes, analysis and scraped items | [`Retention`](/guide/config-db/concepts/retention) | | -| `aws` | Specifies the list of AWS configurations to scrape. | [`[]AWS`](#aws) | | +| `aws` | Specifies the list of AWS configurations to scrape. | [`[]AWS`](#aws) | | ### AWS @@ -35,7 +35,7 @@ The registry has an [AWS](/registry/aws) Helm chart that provides a pre-configur | `exclude` | AWS resources to exclude from scraping | `[]string` | | | `include` | AWS resources to include for scraping | `[]string` | | | `properties` | Custom templatable properties for the scraped config items. | [`[]ConfigProperty`](/reference/config-db/properties) | | -| `transform` | Field to transform result | [`Transform`](/guide/config-db/concepts/transform) | | +| `transform` | Field to transform result | [`Transform`](/guide/config-db/concepts/transform) | | | `tags` | set custom tags on the scraped config items | `map[string]string` | | ## CloudTrail diff --git a/mission-control/docs/guide/config-db/scrapers/azure.md b/mission-control/docs/guide/config-db/scrapers/azure.md index 23fa669..e911ef3 100644 --- a/mission-control/docs/guide/config-db/scrapers/azure.md +++ b/mission-control/docs/guide/config-db/scrapers/azure.md @@ -19,12 +19,12 @@ The Azure scrapers scrapes your azure account to fetch all the resources & save ## Scraper -| Field | Description | Scheme | Required | -| ----------- | ---------------------------------------------------------------------------- | -------------------------------------------- | -------- | -| `logLevel` | Specify the level of logging. | `string` | | -| `schedule` | Specify the interval to scrape in cron format. Defaults to every 60 minutes. | `string` | | +| Field | Description | Scheme | Required | +| ----------- | ---------------------------------------------------------------------------- | -------------------------------------------------- | -------- | +| `logLevel` | Specify the level of logging. | `string` | | +| `schedule` | Specify the interval to scrape in cron format. Defaults to every 60 minutes. | `string` | | | `retention` | Settings for retaining changes, analysis and scraped items | [`Retention`](/guide/config-db/concepts/retention) | | -| `azure` | Azure scrape config | [`[]Azure`](#azure) | | +| `azure` | Azure scrape config | [`[]Azure`](#azure) | | ### Azure @@ -38,7 +38,7 @@ The Azure scrapers scrapes your azure account to fetch all the resources & save | `clientSecret` | Microsoft Entra ID app client secret | _EnvVar_ | | | `exclusions` | Specifies the Azure projects to scrape | [`Exclusion`](#exclusion) | | | `properties` | Custom templatable properties for the scraped config items. | [`[]ConfigProperty`](/reference/config-db/properties) | | -| `transform` | Field to transform result | [`Transform`](/guide/config-db/concepts/transform) | | +| `transform` | Field to transform result | [`Transform`](/guide/config-db/concepts/transform) | | | `tags` | Set custom tags on the scraped config items | `map[string]string` | | :::note diff --git a/mission-control/docs/guide/playbooks/actions/index.md b/mission-control/docs/guide/playbooks/actions/index.md index 9012edd..79c666a 100644 --- a/mission-control/docs/guide/playbooks/actions/index.md +++ b/mission-control/docs/guide/playbooks/actions/index.md @@ -7,21 +7,21 @@ sidebar_position: 3 Actions are the fundamental tasks executed by a playbook. A playbook can comprise multiple actions, which are executed sequentially. If any action encounters an error and fails, the execution of the playbook is halted. -| Field | Description | Scheme | Required | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------- | -------- | -| `name` | Name of action. | `string` | `true` | +| Field | Description | Scheme | Required | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------- | -------- | +| `name` | Name of action. | `string` | `true` | | `runsOn` | Specify the [runners](/guide/playbooks/concepts/runners) that can run this action. One will be chosen on random. When empty, the playbook will run on the main instance itself | `[]string` | | -| `templatesOn` | Specify where the templating of the action spec should occur | `host` or `agent` | | -| `delay` | A delay before running the action e.g. `8h` | `Duration` or [`Expression`](../concepts/expression) | | -| `filter` | Whether to run the step or not | [`Expression`](../concepts/expression) | | -| `timeout` | Timeout on this action. | `Duration` | | -| `azureDevopsPipeline` | | [AzureDevops](./azure_devops_pipeline) | | -| `exec` | Specify exec of action. | [Exec](./exec) | | -| `gitops` | Specify gitops of action. | [Gitops](./gitops) | | -| `http` | Specify http of action. | [Http](./http) | | -| `sql` | Specify sql of action. | [Sql`](./sql) | | -| `pod` | Specify pod of action. | [Pod](./pod) | | -| `notification` | Specify notification of action. | [Notification](./notification) | | +| `templatesOn` | Specify where the templating of the action spec should occur | `host` or `agent` | | +| `delay` | A delay before running the action e.g. `8h` | `Duration` or [`Expression`](../concepts/expression) | | +| `filter` | Whether to run the step or not | [`Expression`](../concepts/expression) | | +| `timeout` | Timeout on this action. | `Duration` | | +| `azureDevopsPipeline` | | [AzureDevops](./azure_devops_pipeline) | | +| `exec` | Specify exec of action. | [Exec](./exec) | | +| `gitops` | Specify gitops of action. | [Gitops](./gitops) | | +| `http` | Specify http of action. | [Http](./http) | | +| `sql` | Specify sql of action. | [Sql`](./sql) | | +| `pod` | Specify pod of action. | [Pod](./pod) | | +| `notification` | Specify notification of action. | [Notification](./notification) | | :::note Specify one or more actions; but at least one. diff --git a/mission-control/docs/guide/playbooks/concepts/expression.md b/mission-control/docs/guide/playbooks/concepts/expression.md index af5eec6..8dcb6da 100644 --- a/mission-control/docs/guide/playbooks/concepts/expression.md +++ b/mission-control/docs/guide/playbooks/concepts/expression.md @@ -1,7 +1,7 @@ --- title: Expressions sidebar_custom_props: - icon: hugeicons:code + icon: hugeicons:code --- Playbook event filters use [Common Expression Language (CEL)](https://github.com/google/cel-go). diff --git a/mission-control/docs/guide/playbooks/webhooks.md b/mission-control/docs/guide/playbooks/webhooks.md index 95d0381..b9def60 100644 --- a/mission-control/docs/guide/playbooks/webhooks.md +++ b/mission-control/docs/guide/playbooks/webhooks.md @@ -3,7 +3,6 @@ title: Webhook Triggers sidebar_position: 4 sidebar_custom_props: icon: material-symbols-light:webhook - --- Playbooks can also be triggered via webhooks. When a webhook is configured, mission-control listens on the specified endpoint and any calls to the endpoint triggers the playbook. diff --git a/mission-control/docs/guide/topology/index.md b/mission-control/docs/guide/topology/index.md index 100599b..49d438a 100644 --- a/mission-control/docs/guide/topology/index.md +++ b/mission-control/docs/guide/topology/index.md @@ -9,7 +9,6 @@ pagination_next: guide/canary-checker/health-checks pagination_prev: guide/playbooks/index sidebar_custom_props: icon: topology - --- A topology is a representation of logical system made up of components and sub-components. diff --git a/mission-control/docs/guide/topology/lookups/exec.md b/mission-control/docs/guide/topology/lookups/exec.md index c891f85..7e3de44 100644 --- a/mission-control/docs/guide/topology/lookups/exec.md +++ b/mission-control/docs/guide/topology/lookups/exec.md @@ -49,11 +49,11 @@ spec: // highlight-end ``` -| Field | Description | Scheme | Required | -| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | -------- | -| **`script`** | Script can be a inline script or a path to a script that needs to be executed. On windows executed via powershell and in darwin and Linux executed using bash. | `Path`, `Bash`or`Powershell` | Yes | +| Field | Description | Scheme | Required | +| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -------- | +| **`script`** | Script can be a inline script or a path to a script that needs to be executed. On windows executed via powershell and in darwin and Linux executed using bash. | `Path`, `Bash`or`Powershell` | Yes | | `display` | Template to display server response in text (overrides default bar format for UI) | [_Template_](/guide/topology/concepts/templating) | | -| `labels` | Labels for the check | Labels | | +| `labels` | Labels for the check | Labels | | | `transform` | Template to transform results by excluding or including certain fields in result | [_Template_](/guide/topology/concepts/templating) | | ## Results diff --git a/mission-control/docs/guide/topology/lookups/kubernetes.md b/mission-control/docs/guide/topology/lookups/kubernetes.md index d85d4c2..9a4b0a6 100644 --- a/mission-control/docs/guide/topology/lookups/kubernetes.md +++ b/mission-control/docs/guide/topology/lookups/kubernetes.md @@ -10,16 +10,16 @@ The Kubernetes component lookup fetches kubernetes resources to be used as compo ``` -| Field | Description | Scheme | Required | -| --------- | ----------------------------------------------------------------------------------- | --------------------------------------- | -------- | -| display | Template to display query results in text (overrides default bar format for UI) | [_Template_](/guide/topology/concepts/templating) | | -| ignore | Ignore the specified resources from the fetched resources. Can be a glob pattern. | _[]string_ | | -| **kind** | Specifies the kind of Kubernetes object for interaction | _string_ | Yes | -| labels | Labels for the check | _string_ | | -| namespace | Specifies namespace for Kubernetes object | [_ResourceSelector_](#resourceselector) | | -| ready | Boolean value of true or false to query and display resources based on availability | _bool_ | | -| resource | Queries resources related to specified Kubernetes object | [_ResourceSelector_](#resourceselector) | | -| transform | Template to transform results to | [_Template_](/guide/topology/concepts/templating) | | +| Field | Description | Scheme | Required | +| --------- | ----------------------------------------------------------------------------------- | ------------------------------------------------- | -------- | +| display | Template to display query results in text (overrides default bar format for UI) | [_Template_](/guide/topology/concepts/templating) | | +| ignore | Ignore the specified resources from the fetched resources. Can be a glob pattern. | _[]string_ | | +| **kind** | Specifies the kind of Kubernetes object for interaction | _string_ | Yes | +| labels | Labels for the check | _string_ | | +| namespace | Specifies namespace for Kubernetes object | [_ResourceSelector_](#resourceselector) | | +| ready | Boolean value of true or false to query and display resources based on availability | _bool_ | | +| resource | Queries resources related to specified Kubernetes object | [_ResourceSelector_](#resourceselector) | | +| transform | Template to transform results to | [_Template_](/guide/topology/concepts/templating) | | ## ResourceSelector diff --git a/mission-control/docs/guide/topology/lookups/prometheus.md b/mission-control/docs/guide/topology/lookups/prometheus.md index d14b70d..d009039 100644 --- a/mission-control/docs/guide/topology/lookups/prometheus.md +++ b/mission-control/docs/guide/topology/lookups/prometheus.md @@ -32,11 +32,11 @@ spec: // highlight-end ``` -| Field | Description | Scheme | Required | -| ----------- | --------------------------------- | ---------------------------------- | -------- | +| Field | Description | Scheme | Required | +| ----------- | --------------------------------- | ----------------------------------------------- | -------- | | `display` | Template to display the result in | [Template](/guide/topology/concepts/templating) | | -| **`host`** | Address of the Prometheus server | string | Yes | -| **`query`** | PromQL query | string | Yes | +| **`host`** | Address of the Prometheus server | string | Yes | +| **`query`** | PromQL query | string | Yes | ## Results diff --git a/mission-control/docs/integrations/aws/getting-started.md b/mission-control/docs/integrations/aws/getting-started.md index da5cc0a..34c299d 100644 --- a/mission-control/docs/integrations/aws/getting-started.md +++ b/mission-control/docs/integrations/aws/getting-started.md @@ -5,10 +5,8 @@ sidebar_custom_props: icon: getting-started --- - import Schema from '@site/modules/mission-control-registry/charts/aws/values.schema.json' - The AWS chart catalog [scraper](/guide/config-db/scrapers/aws) that: - Scrapes AWS Resources and detects changes in the resource definition @@ -16,7 +14,6 @@ The AWS chart catalog [scraper](/guide/config-db/scrapers/aws) that: - Ingests cost data from AWS Cost & Usage Reporting - Links AWS EKS resources to the corresponding Kubernetes resources - :::info Prerequisites - IAM Role for scraping AWS API's @@ -26,9 +23,7 @@ For Cost & Usage Reporting - [Cost and Usage Reports](https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html) are configured with an [Athena](https://docs.aws.amazon.com/cur/latest/userguide/use-athena-cf.html) table - The `AWSQuicksightAthenaAccess` policy or similar is attached to config-db IAM role -::: - - + ::: @@ -36,7 +31,7 @@ For Cost & Usage Reporting 1. Configure the `config-db-sa` service account with a [AWS IAM Pod Identity / Role](/integrations/aws/iam?type=pod) 2. Install the [mission-control-aws](https://artifacthub.io/packages/helm/flanksource/mission-control-aws) chart - - +/> @@ -66,7 +60,6 @@ When you go to the catalog now, you can now see all the AWS Resources - ## Next Steps @@ -93,8 +86,6 @@ When you go to the catalog now, you can now see all the AWS Resources + - - - diff --git a/mission-control/docs/integrations/aws/iam.md b/mission-control/docs/integrations/aws/iam.md index f385242..54c5379 100644 --- a/mission-control/docs/integrations/aws/iam.md +++ b/mission-control/docs/integrations/aws/iam.md @@ -4,7 +4,6 @@ sidebar_custom_props: icon: logos:aws-iam --- - Depending on how you want to use Mission Control you need to create an IAM role for mission control to use: | Use Case | Role | @@ -74,6 +73,7 @@ You can also create a new policy with just the permissions required by Mission C ## Configure IAM Roles for Mission Control + @@ -131,7 +131,6 @@ You can also create a new policy with just the permissions required by Mission C eksctl create iamserviceaccount --cluster $CLUSTER -c eksctl.yaml ``` - @@ -145,7 +144,8 @@ You can also create a new policy with just the permissions required by Mission C 1. Ensure the [AWS Pod Identity Agent](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html) is configured and running 1. Create a mapping file for `eksctl` - ```yaml title="eksctl.yaml" + + ```yaml title="eksctl.yaml" podIdentityAssociations: - namespace: mission-control serviceAccountName: mission-control-sa @@ -179,33 +179,34 @@ You can also create a new policy with just the permissions required by Mission C namespace: mission-control attachPolicyARNs: - "arn:aws:iam::aws:policy/ReadOnlyAccess" - ``` -

- -

- -

If you are using a pre-existing IAM role when creating a pod identity association, you must configure the role to trust the newly introduced EKS service principal (`pods.eks.amazonaws.com`)

- - ```json title="iam-trust-policy.json" - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "Service": "pods.eks.amazonaws.com" - }, - "Action": ["sts:AssumeRole", "sts:TagSession"] - } - ] - } - ``` + ``` + +

+ +

+ +

If you are using a pre-existing IAM role when creating a pod identity association, you must configure the role to trust the newly introduced EKS service principal (`pods.eks.amazonaws.com`)

+ + ```json title="iam-trust-policy.json" + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Principal": { + "Service": "pods.eks.amazonaws.com" + }, + "Action": ["sts:AssumeRole", "sts:TagSession"] + } + ] + } + ``` - + -
+
-3. Apply the Pod Identities using `eksctl` +1. Apply the Pod Identities using `eksctl` ```bash eksctl create podidentityassociation -c eksctl.yaml @@ -213,8 +214,6 @@ You can also create a new policy with just the permissions required by Mission C

- - 1. Ensure the [AWS Pod Identity Agent](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html) is configured and running @@ -222,43 +221,48 @@ You can also create a new policy with just the permissions required by Mission C 2. Create `main.tf` ```hcl title="main.tf" file=/docs/partials/_pod_identity.tf + ``` -

+ +

+ 3. Apply the terraform ```bash TF_VAR_role=$CLUSTER terraform apply ``` -

+

1. Setup variables - ```bash - # The name of the EKS cluster mission control is being deployed to - export CLUSTER= - # the default namespace the mission-control helm chart uses - export NAMESPACE=mission-control - ``` -

+ + ```bash + # The name of the EKS cluster mission control is being deployed to + export CLUSTER= + # the default namespace the mission-control helm chart uses + export NAMESPACE=mission-control + ``` + +

1. Create a cloudformation template ```yaml title="mission-control-iam-cloudformation.yaml" file=/docs/partials/_pod_identity.yaml - ``` -

-2. Create a new stack - ```bash - aws cloudformation deploy \ - --stack-name mission-control-roles \ - --template-file file://mission-control-iam-cloudformation.yaml \ - --parameter-overrides Cluster==$CLUSTER Namespace=$NAMESPACE - ``` -

+ ``` +

+1. Create a new stack + ```bash + aws cloudformation deploy \ + --stack-name mission-control-roles \ + --template-file file://mission-control-iam-cloudformation.yaml \ + --parameter-overrides Cluster==$CLUSTER Namespace=$NAMESPACE + ``` +

@@ -280,11 +284,12 @@ First we create a secret called `aws` containing the access key and secret. aws iam create-user --user-name $USER_NAME aws iam attach-user-policy \ - --user-name $USER_NAME \ - --policy-arn arn:aws:iam::aws:policy/ReadOnlyAccess + --user-name $USER_NAME \ + --policy-arn arn:aws:iam::aws:policy/ReadOnlyAccess key=$(aws iam create-access-key --user-name $USER_NAME) ``` -

+ +

2. Create a new secret `aws` containing the access and secret key @@ -293,33 +298,35 @@ First we create a secret called `aws` containing the access key and secret. --from-literal=AWS_ACCESS_KEY_ID=$(echo $key | jq -r '.AccessKey.AccessKeyId') \ --from-literal=AWS_SECRET_ACCESS_KEY=$(echo $key | jq -r '.AccessKey.SecretAccessKey') ``` -

+ +

+ 3. Create a new [connection](/reference/connections) - ```yaml title="aws-connection.yaml" - apiVersion: mission-control.flanksource.com/v1 - kind: Connection - metadata: - name: aws - namespace: mission-control - spec: - region: eu-west-1 - accessKey: - valueFrom: - secretKeyRef: - name: aws - key: AWS_ACCESS_KEY_ID - secretKey: - valueFrom: - secretKeyRef: - name: aws - key: AWS_ACCESS_KEY_ID + ```yaml title="aws-connection.yaml" + apiVersion: mission-control.flanksource.com/v1 + kind: Connection + metadata: + name: aws + namespace: mission-control + spec: + region: eu-west-1 + accessKey: + valueFrom: + secretKeyRef: + name: aws + key: AWS_ACCESS_KEY_ID + secretKey: + valueFrom: + secretKeyRef: + name: aws + key: AWS_ACCESS_KEY_ID - ``` -

+ ``` -1. When creating Scrapers / Registry bundles you can now refer to `connection://mission-control/aws` +

+ +4. When creating Scrapers / Registry bundles you can now refer to `connection://mission-control/aws` - diff --git a/mission-control/docs/integrations/aws/index.md b/mission-control/docs/integrations/aws/index.md index bf83b49..d407d8c 100644 --- a/mission-control/docs/integrations/aws/index.md +++ b/mission-control/docs/integrations/aws/index.md @@ -7,4 +7,3 @@ sidebar_custom_props: import DocCardList from '@theme/DocCardList'; - diff --git a/mission-control/docs/integrations/flux/catalog.md b/mission-control/docs/integrations/flux/catalog.md index 612c3bb..f43502f 100644 --- a/mission-control/docs/integrations/flux/catalog.md +++ b/mission-control/docs/integrations/flux/catalog.md @@ -4,6 +4,7 @@ sidebar_position: 0 sidebar_custom_props: icon: getting-started --- + import { IoIosHeart } from "react-icons/io"; # FluxCD @@ -16,11 +17,8 @@ Mission Control provides built-in support for relating Flux resources to each ot - Build a graph showing how Flux resources connect and depend on each other - Monitor the overall health of your Flux-based GitOps workflows - - - ## Next Steps @@ -28,26 +26,21 @@ Mission Control provides built-in support for relating Flux resources to each ot + Manage & Monitor flux instances. - - Enable ClickOps workflows backed by git. - + - - - - diff --git a/mission-control/docs/integrations/flux/index.md b/mission-control/docs/integrations/flux/index.md index afed989..79f3efa 100644 --- a/mission-control/docs/integrations/flux/index.md +++ b/mission-control/docs/integrations/flux/index.md @@ -5,10 +5,8 @@ sidebar_custom_props: icon: flux --- - ## Flux import DocCardList from '@theme/DocCardList'; - diff --git a/mission-control/docs/integrations/flux/playbooks.md b/mission-control/docs/integrations/flux/playbooks.md index d55843f..3982fc2 100644 --- a/mission-control/docs/integrations/flux/playbooks.md +++ b/mission-control/docs/integrations/flux/playbooks.md @@ -3,12 +3,13 @@ title: Playbooks sidebar_custom_props: icon: playbook --- + # Flux Playbooks import { IoIosCheckmarkCircleOutline } from "react-icons/io"; import Git from '@site/docs/partials/\_git_all.mdx'; - import Schema from '@site/modules/mission-control-registry/charts/playbooks-flux/values.schema.json' - import OpenAPI from '@site/src/components/OpenAPI' +import Schema from '@site/modules/mission-control-registry/charts/playbooks-flux/values.schema.json' +import OpenAPI from '@site/src/components/OpenAPI' Mission control enhances a [flux](https://fluxcd.io/flux) deployment with: @@ -59,7 +60,7 @@ To enable the Flux integration you need - Mission Control [installed](/installation/) - [kubectl](/installation/saas/kubectl) access to the Mission Control instance -::: + ::: 1. Create a github connection

@@ -80,8 +81,6 @@ To enable the Flux integration you need "git.connection": "connection://mission-control/github", }}/> - - 3. Annotate resources with `config.kubernetes.io/origin` The annotation is added by kustomize when the `originAnnotations` build flag is set: diff --git a/mission-control/docs/integrations/flux/topology.md b/mission-control/docs/integrations/flux/topology.md index 8689a70..37e0a79 100644 --- a/mission-control/docs/integrations/flux/topology.md +++ b/mission-control/docs/integrations/flux/topology.md @@ -9,12 +9,14 @@ The Flux topology provides a comprehensive view of your Flux-based GitOps infras 1. **Controllers**: Monitors Flux system pods in the `flux-system` namespace. 2. **Releases**: Tracks HelmReleases with detailed information including: + - Release status and health - Version information - Configuration details - Related pod connections 3. **Kustomizations**: Visualizes Kustomization resources showing: + - Deployment status - Health metrics - Configuration state @@ -33,7 +35,6 @@ Benefits: - Silence notifications at the `Kustomization` or `HelmRelease` level - Efficient troubleshooting of deployment issues- Comprehensive property tracking for all components - ## Getting Started diff --git a/mission-control/docs/integrations/kubernetes/index.md b/mission-control/docs/integrations/kubernetes/index.md index 7930012..bf4f9e3 100644 --- a/mission-control/docs/integrations/kubernetes/index.md +++ b/mission-control/docs/integrations/kubernetes/index.md @@ -5,9 +5,6 @@ sidebar_custom_props: icon: k8s --- - - import DocCardList from '@theme/DocCardList'; - diff --git a/mission-control/docs/integrations/kubernetes/playbooks.md b/mission-control/docs/integrations/kubernetes/playbooks.md index 00b3e65..a099686 100644 --- a/mission-control/docs/integrations/kubernetes/playbooks.md +++ b/mission-control/docs/integrations/kubernetes/playbooks.md @@ -9,7 +9,6 @@ import { IoIosCheckmarkCircleOutline } from "react-icons/io"; import Schema from '@site/modules/mission-control-registry/charts/playbooks-kubernetes/values.schema.json' import OpenAPI from '@site/src/components/OpenAPI' - Self-service playbooks empower teams to manage their Kubernetes resources efficiently: - **Reduced operational overhead**: Teams can perform common tasks without DevOps intervention @@ -41,14 +40,12 @@ The following playbooks are available for use: ## Getting Started - :::info Prerequisites To enable the Kubernetes integration you need: - Mission Control [installed](/installation) - [kubectl](/installation/saas/kubectl) access to the Mission Control instance -::: - + ::: 1. Install the `mission-control-playbooks-kubernetes` helm chart. @@ -60,7 +57,6 @@ If you are using the SaaS, then this needs to be installed on the SaaS vCluster createRepo={false} /> - :::info Note The playbooks chart only needs to be installed once, unlike the `mission-control-kubernetes` chart which is per cluster ::: diff --git a/mission-control/docs/reference/config-db/index.md b/mission-control/docs/reference/config-db/index.md index 5fa9031..f6d4488 100644 --- a/mission-control/docs/reference/config-db/index.md +++ b/mission-control/docs/reference/config-db/index.md @@ -3,7 +3,6 @@ title: Config DB sidebar_position: 4 sidebar_custom_props: icon: config-db - --- import DocCardList from '@theme/DocCardList'; diff --git a/mission-control/docs/reference/playbooks/index.md b/mission-control/docs/reference/playbooks/index.md index b7a0b42..24e790c 100644 --- a/mission-control/docs/reference/playbooks/index.md +++ b/mission-control/docs/reference/playbooks/index.md @@ -3,7 +3,6 @@ title: Playbook sidebar_position: 6 sidebar_custom_props: icon: playbook - --- | Field | Description | Scheme | @@ -14,7 +13,7 @@ sidebar_custom_props: | `on.component` | Run a playbook when a component becomes heathy/unhealthy | [`EventTrigger`](./events#component) | | `on.config` | Run a playbook when a config item is created/updated/deleted or changes state | [`EventTrigger`](./events#config) | | `on.webhook` | Run a playbook when a webhook is called | [`Webhook`](./webhooks) | -| `runsOn` | Which [runner](/guide/playbooks/concepts/runners) (agent) to run the playbook on | [`[]Agent`](/reference/types#agent) | +| `runsOn` | Which [runner](/guide/playbooks/concepts/runners) (agent) to run the playbook on | [`[]Agent`](/reference/types#agent) | | `templatesOn` | Where the templating of actions should occur
For `host` the templating occurs on the mission control instance before being passed to the agent
For `agent` the templating occurs on the agent/runner where there might be secrets not accessible by the primary instance. | `host` or `agent` | | `checks` | Which health checks can this playbook run on | [`[]ResourceSelector`](/reference/resource-selector) | | `configs` | Which config items can this playbook run on | [`[]ResourceSelector`](/reference/resource-selector) | @@ -73,22 +72,22 @@ scheme: 'string', ## Actions -| Field | Description | Scheme | Required | -| --------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- | -------- | -| **`name`** | Step Name | `string` | `true` | +| Field | Description | Scheme | Required | +| --------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- | -------- | +| **`name`** | Step Name | `string` | `true` | | `runsOn` | Which [runner](/guide/playbooks/concepts/runners) (agent) to run the action on | [`[]Agent`](/reference/types#agent) | | -| `templatesOn` | Where templating (and secret management) of actions should occur | `host` or `agent` | | -| `delay` | A delay before running the action e.g. `8h` | [`Duration`](/reference/types#duration) or [CEL](/reference/scripting/cel) with [Playbook Context](./context) | | -| `filter` | Conditionally run an action | [CEL](/reference/scripting/cel) with [Playbook Context](./context) | | -| `timeout` | Timeout on this action. | [`Duration`](/reference/types#duration) | | -| `azureDevopsPipeline` | Trigger a pipeline run | [AzureDevops](/guide/playbooks/actions/azure_devops_pipeline) | | -| `exec` | Run a script e.g. to use `kubectl` or `aws` CLI's | [Exec](/guide/playbooks/actions/exec) | | -| `github` | Trigger Github Action | [Github Action](/guide/playbooks/actions/github) | | -| `gitops` | Update a git repository (directly or via pull request) | [Gitops](/guide/playbooks/actions/gitops) | | -| `http` | Call an HTTP Endpoint | [Http](/guide/playbooks/actions/http) | | -| `sql` | Execute a SQL query | [Sql](/guide/playbooks/actions/sql) | | -| `pod` | Run a kubernetes pod. | [Pod](/guide/playbooks/actions/pod) | | -| `notification` | Specify notification of action. | [Notification](/guide/playbooks/actions/notification) | | +| `templatesOn` | Where templating (and secret management) of actions should occur | `host` or `agent` | | +| `delay` | A delay before running the action e.g. `8h` | [`Duration`](/reference/types#duration) or [CEL](/reference/scripting/cel) with [Playbook Context](./context) | | +| `filter` | Conditionally run an action | [CEL](/reference/scripting/cel) with [Playbook Context](./context) | | +| `timeout` | Timeout on this action. | [`Duration`](/reference/types#duration) | | +| `azureDevopsPipeline` | Trigger a pipeline run | [AzureDevops](/guide/playbooks/actions/azure_devops_pipeline) | | +| `exec` | Run a script e.g. to use `kubectl` or `aws` CLI's | [Exec](/guide/playbooks/actions/exec) | | +| `github` | Trigger Github Action | [Github Action](/guide/playbooks/actions/github) | | +| `gitops` | Update a git repository (directly or via pull request) | [Gitops](/guide/playbooks/actions/gitops) | | +| `http` | Call an HTTP Endpoint | [Http](/guide/playbooks/actions/http) | | +| `sql` | Execute a SQL query | [Sql](/guide/playbooks/actions/sql) | | +| `pod` | Run a kubernetes pod. | [Pod](/guide/playbooks/actions/pod) | | +| `notification` | Specify notification of action. | [Notification](/guide/playbooks/actions/notification) | | > Only 1 action should be specified per step diff --git a/mission-control/docs/reference/topology/_lookup.md b/mission-control/docs/reference/topology/_lookup.md index 8a6b8ec..299fd34 100644 --- a/mission-control/docs/reference/topology/_lookup.md +++ b/mission-control/docs/reference/topology/_lookup.md @@ -1,10 +1,10 @@ -| Field | Description | Type | Required | -| ------------ | -------------------------------------------- | ---------------------------------------------- | -------- | -| `catalog` | Lookup catalogs in configDB. | [`[]Catalog`](/guide/topology/lookups/catalog) | | -| `exec` | Lookup by running (bash/powershell) scripts. | [`[]Exec`](/guide/topology/lookups/exec) | | -| `kubernetes` | Lookup kubernetes resources | [`[]Kubernetes`](/guide/topology/lookups/kubernetes) | | -| `http` | Lookup an HTTP endpoint. | [`[]HTTP`](/guide/topology/lookups/http) | | -| `mongodb` | Query records from a MongoDB /guide/canary-checker/reference/database. | [`[]MongoDB`](/guide/topology/lookups/mongo) | | -| `sql` | Query records from a MSSQL /guide/canary-checker/reference/database. | [`[]SQL`](/guide/topology/lookups/sql) | | -| `redis` | Query records from a Redis server. | [`[]Redis`](/guide/topology/lookups/redis) | | -| `prometheus` | Query metrics from Prometheus. | [`[]Prometheus`](/guide/topology/lookups/prometheus) | | +| Field | Description | Type | Required | +| ------------ | ---------------------------------------------------------------------- | ---------------------------------------------------- | -------- | +| `catalog` | Lookup catalogs in configDB. | [`[]Catalog`](/guide/topology/lookups/catalog) | | +| `exec` | Lookup by running (bash/powershell) scripts. | [`[]Exec`](/guide/topology/lookups/exec) | | +| `kubernetes` | Lookup kubernetes resources | [`[]Kubernetes`](/guide/topology/lookups/kubernetes) | | +| `http` | Lookup an HTTP endpoint. | [`[]HTTP`](/guide/topology/lookups/http) | | +| `mongodb` | Query records from a MongoDB /guide/canary-checker/reference/database. | [`[]MongoDB`](/guide/topology/lookups/mongo) | | +| `sql` | Query records from a MSSQL /guide/canary-checker/reference/database. | [`[]SQL`](/guide/topology/lookups/sql) | | +| `redis` | Query records from a Redis server. | [`[]Redis`](/guide/topology/lookups/redis) | | +| `prometheus` | Query metrics from Prometheus. | [`[]Prometheus`](/guide/topology/lookups/prometheus) | | diff --git a/mission-control/docs/reference/topology/properties.md b/mission-control/docs/reference/topology/properties.md index a1f5467..e999613 100644 --- a/mission-control/docs/reference/topology/properties.md +++ b/mission-control/docs/reference/topology/properties.md @@ -34,11 +34,11 @@ title: Property ## Config Lookup -| Field | Description | Scheme | Required | -| --------------- | -------------------------------------------------------- | ---------------------------------- | -------- | -| `config.name` | The name of the config item. | `string` | | -| `config.type` | The type of config item. | `string` | | -| `config.labels` | Match labels of the config item, all labels must match | `map[string]string` | | -| `field` | A JSONPath expression to lookup the value in the config. | `string` | `true` | +| Field | Description | Scheme | Required | +| --------------- | -------------------------------------------------------- | ------------------------------------------------ | -------- | +| `config.name` | The name of the config item. | `string` | | +| `config.type` | The type of config item. | `string` | | +| `config.labels` | Match labels of the config item, all labels must match | `map[string]string` | | +| `field` | A JSONPath expression to lookup the value in the config. | `string` | `true` | | `display` | Apply transformations to the value. | [`Display`](/guide/topology/concepts/templating) | | -| `id` | The UUID of config item, rarely used | `string` | | +| `id` | The UUID of config item, rarely used | `string` | | diff --git a/modules/canary-checker b/modules/canary-checker index af09c0c..fc63300 160000 --- a/modules/canary-checker +++ b/modules/canary-checker @@ -1 +1 @@ -Subproject commit af09c0c243fbf427c04d0b78dc7ea0a6691467ac +Subproject commit fc63300c2d101d3cb3a031dda75fb64b0d9905ec diff --git a/modules/config-db b/modules/config-db index f4af6b3..bd9160b 160000 --- a/modules/config-db +++ b/modules/config-db @@ -1 +1 @@ -Subproject commit f4af6b30d53f5a231c2a13adea3b10291d2bcc6b +Subproject commit bd9160b52094c3d6782215f6df3ae2a1a2b095ad diff --git a/modules/duty b/modules/duty index 17e5747..79ebc04 160000 --- a/modules/duty +++ b/modules/duty @@ -1 +1 @@ -Subproject commit 17e5747f912e6da1a24117dd5c48e921d4488832 +Subproject commit 79ebc04175f75a87d857cb2bf8c25ea6664d041f diff --git a/modules/mission-control b/modules/mission-control index 5b91721..1fb216a 160000 --- a/modules/mission-control +++ b/modules/mission-control @@ -1 +1 @@ -Subproject commit 5b91721cb713cc3b8e536fd9012ddafa6cac835a +Subproject commit 1fb216ad7d66543312a4400e9bf12e414526c369 diff --git a/modules/mission-control-chart b/modules/mission-control-chart index a681217..6e75633 160000 --- a/modules/mission-control-chart +++ b/modules/mission-control-chart @@ -1 +1 @@ -Subproject commit a6812177a1cc80822c8980232955244306b89c38 +Subproject commit 6e756337145ca0b9227001964b71246c4d071df4 diff --git a/modules/mission-control-registry b/modules/mission-control-registry index a9eb446..93cb59b 160000 --- a/modules/mission-control-registry +++ b/modules/mission-control-registry @@ -1 +1 @@ -Subproject commit a9eb44623ccaecc1ec0877594b86c37a0d7af9c8 +Subproject commit 93cb59bb56dc9eaf8109e66abda2b2b94066439e