Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to skip ConfigMap creation #41

Closed
wants to merge 1 commit into from
Closed

Conversation

k0da
Copy link
Contributor

@k0da k0da commented Sep 22, 2021

There are cases where zones are different but plugins are. In order to
avoid duplication of whole zone block configuration, allow to disable
config map creation and let it to be managable externally, where it is
possible to keep plugins configuration same, but change zone definition
only.

Signed-off-by: Dinar Valeev [email protected]

There are cases where zones are different but plugins are. In order to
avoid duplication of whole zone block configuration, allow to disable
config map creation and let it to be managable externally, where it is
possible to keep plugins configuration same, but change zone definition
only.

Signed-off-by: Dinar Valeev <[email protected]>
@ErikLundJensen
Copy link

This change is important as it enables using CoreDNS as an external nameserver for Ingress/Gateway resources. For example the k8gb, which is a Geo redundant load balancer, manage the definition of the Corefile.

@hagaibarel
Copy link
Collaborator

Please rebase and bump the chart version

@cep21
Copy link

cep21 commented May 19, 2024

Bump:

I woud love to manage the configmap file in a syntax that more closely matches coredns itself, rather than YAML. This is difficult to do in the current helm chart.

@cep21 cep21 mentioned this pull request May 19, 2024
4 tasks
@cep21
Copy link

cep21 commented May 19, 2024

Hi,

If the PR is safe, can we merge it in #167? I did the requested "rebase and bump", but it only lasts as long as the next version.

I cannot edit other people's PRs, so I had to make a new one.

@hagaibarel
Copy link
Collaborator

Closing in favor of #167

@hagaibarel hagaibarel closed this May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants