Skip to main content

Infrastructure Services

The services below are required by the monorepo, and are owned by the Infrastructure team (#ask-infra).

Secret Management: Vault​

URL: https://vault.int.camunda.com/

A self-hosted Hashicorp Vault instance.

For the monorepo, it is used to store secrets for GHA workflows (the use of standard GitHub Actions Secrets is discouraged). Example usage.

Relevant internal docs:

CI: Self-Hosted GitHub Actions Runners​

Self-hosted runners are used to provide larger-than-standard GHA runners at lower costs than GitHub would charge.

The provided runners are autoscaled based on demand and run in Kubernetes clusters (GCP, AWS). The monorepo uses the prod environment of the runners.

Example usage.

Relevant internal docs:

Dependency Management: Renovate​

Renovate is used to create/merge PRs to bump dependencies. The SaaS version is used.

Relevant documentation:

Monitoring (CI Analytics)​

The monorepo uses the prod environment of the following services.

BigQuery​

The metrics collection from the monorepo CI (CI Analytics) uses GCP BigQuery as a data sink.

Prometheus​

Metric collection system.

URL: https://monitor.int.camunda.com/

  • Collects metrics from various sources, e.g. self-hosted runners and GitHub merge queue.
  • Alerting rules can be set up for metric violations.

Grafana​

Metric visualization system. Uses Prometheus and BigQuery as data sources.

URL: https://dashboard.int.camunda.com/

Relevant links:

Infra Global GitHub Actions​

The monorepo CI makes use of the camunda/infra-global-github-actions reusable workflows and composite actions to avoid duplicating pipeline code and share functionality with other parts of Engineering.