Configuration Guide

Ground Control Configuration

Ground Control, the dedicated portal for managing and visualizing your algorithm deployments, can be enabled or disabled according to your needs.

To enable or disable Ground Control, update the values.yaml file as follows:

groundControl:
  enabled: true

In this configuration, setting groundControl.enabled to true will activate Ground Control. If you prefer not to use Ground Control, simply set this value to false.

Database Configuration

OuterSpace Operator relies exclusively on PostreSQL. However, you can either utilize a PostgreSQL database that can be managed (like Google Cloud SQL) or directly deployed within your Kubernetes cluster using the Bitnami's PostgreSQL Helm chart. For the latter, you need to enable it in the values.yaml file:

postgresql:
  enabled: true

In this configuration, setting postgresql.enabled to true will install PostgreSQL directly in your Kubernetes cluster using Bitnami's PostgreSQL Helm chart.

Monitoring Configuration

When deploying on GKE, OuterSpace Operator can leverage Managed Prometheus for monitoring or pull in Prometheus using its Helm chart. Update the values.yaml file with the relevant settings.

prometheus:
  managed: false

In this configuration, setting prometheus.managed to false means that Managed Prometheus will not be used. Instead, Prometheus will be pulled in via its Helm chart.

Ingress Configuration

The OuterSpace Operator provides flexibility when it comes to managing ingress for your algorithms. It can integrate with multiple ingress classes including NGINX, Kong, or GCE. You can specify your choice in the values.yaml file:

ingress:
  class: "nginx"

In this configuration, replace nginx with your preferred ingress class (nginx, kong, or gce).

Warning

Ensure that the selected ingress controller is properly installed and configured in your Kubernetes cluster.