Installation

Remote Operator setup produces two separate things.

Project template

byoc-operator.yaml belongs in your chart’s templates/ directory. It contains the project-specific image and Kubernetes resources for the capabilities selected in the dashboard.

The current dashboard renders it with namespace scope. Review at least:

• the image and digest;
• ServiceAccount and Role/RoleBinding rules;
• Secrets and environment variables;
• outbound destinations; and
• log collector resources when enabled.

Commit the template to the chart only after that review.

Installation values

Every installed environment gets its own values:

remoteOperator:
  registrationToken: "..."
  encryptionKey: "..."
  collectorToken: "..."

These values identify and protect one installation. Keep them in the secret-delivery system you already use for Helm values. Do not commit them to the chart, reuse them across customers, or place them in values.yaml defaults.

Release it like the rest of your chart

Remote Operator does not replace your Helm release process. Test the chart, publish it, and roll it out through the same path as the rest of your application.

Enable it one installation at a time. A connected installation appears under Deployments in Alien.