This chart installs the remote services for Lagoon. Install this chart into the cluster you want to deploy workloads to.

None.

After this chart is installed, Lagoon needs to be configured to deploy to this cluster. This is outside the scope of this README.

NOTE: This chart must be installed into the lagoon namespace because software that consumes lagoon services inside the cluster assumes that services are available at *.lagoon.svc.

helm upgrade --install --create-namespace --namespace lagoon lagoon-remote ./charts/lagoon-remote

the included docker-host needs privileged permissions:

oc -n lagoon adm policy add-scc-to-user privileged  -z lagoon-remote-docker-host

helm uninstall lagoon-remote

• The kubernetesbuilddeploy serviceaccount is bound to cluster-admin.

This section only applies if using NATS for ssh-portal support. NATS and ssh-portal are currently disabled by default.

The minimum configuration required to enable NATS is:

nats:
  enabled: true
  cluster:
    name: lagoon-remote-example

Note that the cluster name used in Lagoon Core and each Lagoon Remote must be unique in order for NATS routing to work correctly.

See the Lagoon Core chart README for instructions for securing NATS.