Skip to content
Percona Everest Documentation

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Split-Horizon DNS feature for Percona Server for MongoDB

Introduction

Split-Horizon DNS for Percona Server for MongoDB (PSMDB) allows database administrators to expose ReplicaSet Pods with custom domain names, both inside and outside the Kubernetes cluster, without conflicting with the default DNS configuration.

Why Split-Horizon DNS matters?

This is useful in scenarios such as:

  • Performing maintenance tasks, like copying data from one ReplicaSet to another cluster.

  • Providing temporary or alternative domain names for direct Pod access without impacting the default DNS configuration.

  • Allow database administrators to assign custom domain names to the exposed Pods.

  • Provide Percona Everest users with the capability to obtain connection URLs for the exposed Pods using external domains.

Prerequisites

Before you begin, make sure you:

These concepts are essential for correctly configuring external domain access to exposed Pods in Percona Everest.

Limitations of Split-Horizon DNS

Some limitations apply when using Split-Horizon DNS. For more details, refer to the limitations section.