Skip to main content
Tungsten Clustering

Configure Database Hostnames (Optional)

note

This step is only required if your database hostnames cannot be resolved via DNS in your Kubernetes cluster.

If your databases are accessible via DNS (e.g., db1.example.com), skip this step and ensure your cluster topology uses the correct FQDNs.

If DNS resolution is NOT available, uncomment and configure the hostAliases section in deployment.yaml (lines 21-30), for example:

hostAliases:
- ip: "10.0.1.10" # Replace with actual db1 IP
hostnames:
- "db1"
- ip: "10.0.1.11" # Replace with actual db2 IP
hostnames:
- "db2"
- ip: "10.0.1.12" # Replace with actual db3 IP
hostnames:
- "db3"