Configuring database access on a self-hosted instance

On self-hosted instance, you configure the following options related to database access:

• The type of service to use for the database connections

• DNS connection information

Selecting the service type

In the database_access section of the Helm chart, you configure the service type as the value of the serviceType setting.

serviceType: "NodePort" # Either LoadBalancer|NodePort

The options are:

• NodePort - Indicates to use a node port for each database connection. Node ports typically allow a larger number of database connections. However, you cannot use the node port option with a serverless node port solution such as Fargate.

• LoadBalancer - Indicates to use a load balancer for each database connection. Most load balancers limit the number of connections to 50 or 100. Note that if you use a serverless node port solution, then you must use the load balancer option.

Configuring the DNS connection options

In the database_access section of the Helm chart, under dns, you configure the DNS connection for the databases.

  dns:
     domain: ""
      kubernetesDomainAnnotation: external-dns.alpha.kubernetes.io/hostname
      labels: {}
      annotations:
        # Default to exposing the dns by HostIP
        external-dns.alpha.kubernetes.io/endpoints-type: HostIP

The settings are:

domain	The DNS domain to use for database connections.
kubernetesDomainAnnotation	The annotation to apply to the service that provides the DNS value to use for each database.
labels	A list of custom labels to apply to the Kubernetes service for each database.
annotations	A list of custom annotations to apply to the Kubernetes service for each database.