Documentation

Single Namespace Mode


Astronomer can be deployed into a single namespace for clusters where obtaining an Admin role isn't possible.

This change can be made directly in the config.yaml

# Disable EFK stack which requires a CluterRole
tags:
  logging: false

# Put the rest of platform in single namespace mode.
# This will only provision Roles, instead of ClusterRoles.
# This also configures Houston to deploy airflows to its own namespace.
global:
  singleNamespace: true

The rest of the config.yaml can go unchanged. An example could look like:

#################################
## Astronomer global configuration
#################################
global:
  # Base domain for all subdomains exposed through ingress
  baseDomain: astro.mydomain.com

  # Name of secret containing TLS certificate
  tlsSecret: astronomer-tls


#################################
## Nginx configuration
#################################
nginx:
  # IP address the nginx ingress should bind to
  loadBalancerIP: 0.0.0.0
  preserveSourceIP: true

###############################
## Single Namespace Mode
###############################

# Disable EFK stack which requires a CluterRole
tags:
  logging: false

# Put the rest of platform in single namespace mode.
# This will only provision Roles, instead of ClusterRoles.
# This also configures Houston to deploy airflows to its own namespace.
global:
  singleNamespace: true

#################################
## SMTP configuration
#################################  

astronomer:
  houston:
    config:
      email:
        enabled: true
        smtpUrl: YOUR_URI_HERE