Catalog Details

• CATEGORY

  traffic-management

• CREATED BY

  Deepak Reddy

• UPDATED AT

  November 23, 2024

• VERSION

  0.0.1

Pattern Snapshot

Related Patterns

traffic-management

Understanding the difference between Edge Relationships

MESHERY4f72

What this pattern does:

ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the Kubernetes API to determine a desired list of DNS records. Unlike KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly—e.g. AWS Route 53 or Google Cloud DNS. In a broader sense, ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.

Caveats and Consideration:

For more information and considerations checkout this repo https://github.com/kubernetes-sigs/external-dns/?tab=readme-ov-file

Compatibility:

Recent Discussions with "meshery" Tag

• Nov 22 | Meshery CI Maintainer: Sangram Rath Vivek Vishal
• Dec 04 | Link Meshery Integrations and Github workflow or local code Shlok Mishra
• Nov 20 | Meshery Development Meeting | Nov 20th 2024 Vivek Vishal
• Nov 10 | Error in "make server" and "make ui-server" Aadarsh Shekhar
• Nov 11 | Difference in dev Environments on port 9081 and 3000 Divyansh Khatri
• Nov 10 | npm run lint:fix error Sankarshan Mishra
• Oct 30 | Getting Meshery locally using Docker Desktop for Meshery UI contribution Davidudale
• Nov 07 | Meshery + GCP Connector Santosh Kumar Doodala
• Oct 24 | Getting error when using utils.SetupContextEnv() when writing tests for relationship command Sujai Gupta
• Nov 16 | Where's the Cortex Integration of Meshmap? Aditya Gupta