Ask an OpenShift Admin Office Hour - DNS and cluster networking
March 26, 2021 | by
DNS forms the backbone of service discovery, both internally and externally, with OpenShift. Did you know OpenShift has separate DNS for Pods and nodes? This episode we’re joined by Christian Hernandez, DNS expert and Technical Marketing Manager for OpenShift, to talk about how DNS is used and configured for both Pods and nodes in the cluster. We also discuss external DNS resolution and how to configure forwarders using the OpenShift DNS Operator.
As always, please see the list below for additional links to specific topics, questions, and supporting materials for the episode!
If you’re interested in more streaming content, please subscribe to the OpenShift.tvstreaming calendar to see the upcoming episode topics and to receive any schedule changes. If you have questions or topic suggestions for the OpenShift Administrator’s Office Hour, please contact us via Discord, Twitter, or come join us live, Wednesdays at 11am EDT / 1500 UTC, on YouTube and Twitch.
Episode 23 recorded stream:
Supporting links for today’s topic:
Use this link to jump straight to where we begin talking about DNS in OpenShift.
OpenShift uses CoreDNS to resolve queries from Pods.
Reference architectures can be a bit of a sensitive topic. Lots of people want them for a myriad of reasons, but Red Hat stopped producing OpenShift reference architectures in the 3.10 timeframe. However, that doesn’t mean we forgot about them! Instead, our partner ecosystem has taken the mantle and creates reference architectures for their hardware or software platform. For example, you can see HPE, NetApp FlexPod, and even VMware reference architectures for OpenShift all on their own websites.
Overview The policy framework in Red Hat Advanced Cluster Management for Kubernetes (RHACM) is a powerful feature that help you to govern your configurations across multiple clusters. You can enforce ...