Remote Operator for existing products
Remote Operator can now join a product you already ship with your own Helm chart or Amazon ECS service. How you release doesn't change. The dashboard generates the chart or template, and the install ends with one command:
helm install operator-<installation-id> ./remote-operator \
--namespace checkout --kube-context customer-1-staging \
--values operator-values.yaml --replace --atomic --wait --timeout 5mRemote Operator is one container that runs next to your application. It only connects out, so the customer's security team has no inbound access to review. Through it, your team runs operations, opens debug sessions, and rolls out upgrades.
Open Set up Remote operator in a project and choose Existing Kubernetes or Amazon ECS Fargate. Before installing, you review the image, the RBAC or IAM it grants, and which Pods it collects logs from.
- Installations: each customer environment shows status, the exact image it runs, and whether its permissions are out of date
- Releases for software Alien didn't ship: record the version each installation runs, see drift, and roll back
- Key rotation: rotate an installation's connection key without reinstalling
- Inside your chart: ship it as a dedicated release or as part of your product's own release