Skip to main content
Version: 0.1 (next)

The hosted control plane

darkshift runs an Infrared control plane at infrared.darkshift.io. It is a self-hosted install like any other, on GKE in Google Cloud, and it is the install darkshift builds and ships Infrared itself on. It releases itself with Infrared's own release flow: each upgrade is a Release of the platform Product, and its release guard checks the upgrade, its SLOs included, and rolls it back if it fails.

On it, you get an org of your own: your own Products, access groups, AgentRoles, model key and Settings, in a namespace of its own. Nothing to install or upgrade.

Get an org​

Orgs on the hosted control plane are opened by darkshift. Book a call or write to [email protected] with:

  • the org name you want (a lowercase name such as acme);
  • the GitHub logins of the people who will set it up, who become its org admins.

We create the org with those logins as its admins (see Create an org). There is no self-service sign-up yet.

Set it up​

  1. Sign in. Open infrared.darkshift.io and choose Sign in with GitHub. Only logins on one of your org's access groups get in. See Sign in with GitHub.
  2. Connect your GitHub organization. In Settings → GitHub, create your org's own GitHub App on a GitHub organization you administer. A GitHub organization belongs to one Infrared org, and no other org can use it. See Connect GitHub.
  3. Create your gitops repo in that GitHub organization. Every promotion is then a pull request you can read there. See Create the gitops repo.
  4. Set your model key in Settings → Model provider, if agents will build Changes. Runs spend on your Anthropic account, and each run reports its cost.
  5. Add people. In Settings → Access groups, add the GitHub logins of your team, each with a role. See Access groups and access.
  6. Create a Product from a repo, a template or a zip, and ask for your first Change. See Products and Deliver a single app.

Where your Products run​

By default, your Products' environments run on the hosted control plane's own cluster, at addresses darkshift gives them, or on your own domains.

To run them in your own cloud instead, give darkshift a role in your Google Cloud project or AWS account (see Cloud accounts). We then build a GKE or EKS workload cluster there from a cluster template, or register a cluster you already have, and allow your org onto it. Clusters are registered by platform admins, so on the hosted control plane that step is ours.

Send a Mac's stack metrics here​

A localred stack sends its metrics to the control plane you are signed in to with ir login, with no setup. Sign ir in to the hosted control plane with an API token from Settings → API tokens, and ir local up connects the stack:

ir login --server https://infrared.darkshift.io/api --token-stdin < <your token file>

Hosted or your own install​

The hosted control plane and an install of your own on GKE or EKS run the same Infrared: Products, Changes, Releases and agents work the same way, and your repos and gitops repo stay in your GitHub organization either way. What an install of your own adds is the cluster itself: you hold the platform admin role, register and build clusters yourself, and choose when to upgrade.