The Actuator component receives events from Control Plane and uses the metadata provided in the events to instantiate the desired configuration on the kubernetes cluster. This can be Kubernetes deployments, domain routing configuration, storage devices, etc.
These environment variables can be provided to the actuator deployment on the cluster. If you are making adjustments to these settings provide the changes to Control Plane support so they will be included when new manifests are generated.
internet-facing
or internal
. When internal is used then you must be on a private network to access the workloads
running in this location. Automated detection of geo-routing is limited in this configuration since the external monitoring
will not be able to reach the endpoints.