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

Provide Access to Pod DNSConfig #2658

Open
forestsword opened this issue Feb 23, 2024 · 3 comments · May be fixed by #2712
Open

Provide Access to Pod DNSConfig #2658

forestsword opened this issue Feb 23, 2024 · 3 comments · May be fixed by #2712
Assignees
Labels
enhancement New feature or request needs triage

Comments

@forestsword
Copy link

Component(s)

collector

Is your feature request related to a problem? Please describe.

I need to be able to add the DNSConfig to the collector pods by way of the Operator. Today this is not exposed.

Describe the solution you'd like

That DNSConfig is exposed as a part of the OpenTelemetryCollector API.

Describe alternatives you've considered

I don't know of another way aside from a custom mutating webhook.

Additional context

No response

@forestsword forestsword added enhancement New feature or request needs triage labels Feb 23, 2024
@yuriolisa yuriolisa self-assigned this Feb 29, 2024
@yuriolisa yuriolisa linked a pull request Mar 5, 2024 that will close this issue
@forestsword
Copy link
Author

As a late follow up, it would be also be helpful to have DNSPolicy configurable.

@pavolloffay
Copy link
Member

@forestsword could you please describe the use-case you are trying to solve?

@forestsword
Copy link
Author

Sure, I'm following some internal best practices for our Kubernetes clusters where we use dnsmasq to cache and prevent overloading coredns.

The policy needs to be set to None and a custom dns configuration provided to use a local dnsmasq instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants