Replies: 2 comments
-
|
@kevsterd you can definitely configure NS+A records statically outside of k8gb controller logic and point to k8gb-enabled clusters. It will work in general. In a fully automated setup, k8gb will do it for you. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Do you have any documentation logic or detail for what the k8gb operator names them or expects them to be. I need to spend some time looking at this however so it could just be my understanding. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just starting to look at this project, however might be missing something :)
All of the examples appear to be managing the upstream DNS zones (regardless if its AWS, Azure, On Prem etc) by adding nameserver records for the exposed K8GB instances.
Has there been any thoughts into being able to add them statically into the upstream resolvers ? Some deployments may not like automation reaching in to add these records. I get static is not always good but dns is pretty good at handling dead resolvers.
Am I missing something ?
Beta Was this translation helpful? Give feedback.
All reactions