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

Feature Request: Add extraVolume configuration #272

Open
jnamdar opened this issue Feb 28, 2024 · 0 comments
Open

Feature Request: Add extraVolume configuration #272

jnamdar opened this issue Feb 28, 2024 · 0 comments

Comments

@jnamdar
Copy link

jnamdar commented Feb 28, 2024

To my knowledge it is possible to specify extra volumes in the upstream CoreDNS helm chart like so (https://github.com/coredns/helm/blob/master/charts/coredns/values.yaml#L236) :

extraVolumes: []
# - name: some-volume-name
#   emptyDir: {}
# optional array of mount points for extraVolumes
extraVolumeMounts: []
# - name: some-volume-name
#   mountPath: /etc/wherever

This would be very useful to do as well in k8s-gateway, for instance my use case would be enabling DNSSEC by adding the dnssec plugin in my k8s-gateway config, generating a key with dnssec-keygen and then mounting that key in the DaemonSet so it can be read by the plugin. Without this, I currently don't know how I would mount that key

DNSSEC plugin doc : https://coredns.io/plugins/dnssec/
Relevant plugin config (the key here is literally named Kexample.org.+013+45330, and its path needs to be specified and available within the CoreDNS Pods) :

example.org {
    dnssec {
        key file Kexample.org.+013+45330
    }
    whoami
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant