Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Set up external-dns on a kubernetes cluster" | Hashnode

Feed/

Discussion

Set up external-dns on a kubernetes cluster

In this article, I'm going to explain how to set up external-dns module in a Kubernetes cluster. This module is useful to generate dynamic URLs when deploying applications in a cluster. It detects components when they are deployed into the cluster an...

Apr 15, 2023·6 min read·yodamad.hashnode.devUpdated May 9, 2023Read the article

#kubernetes

#dns

#exoscale

#external-dns

Written by

Matthieu Vincent

@yodamad · Cusset, France

View profile

TechAdvocate DevSecOps / Cloud platform Lead Architect @ Sopra Steria Speaker @ Devoxx, Snowcamp, Breizhcamp, GitLab Connect and internally Co-Founder of Volcamp IT Conference @ Clermont-Fd (https://volcamp.io) GitLab Hero

Responses1

Markdown supported · ⌘↵ to post

Maxime

Apr 17, 2023

Wouldn't that have also worked with a wildcard DNS? Then, no need for an external DNS service. Although less secure (filter would be on ingress, not in DNS resolving).

Matthieu Vincent

Apr 17, 2023

In my point of view, it's a security risk and a bad practice, that's why I prefer this way even if a bit complicated (not that much when everything is setup)