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
Add the ability to modify the dnsconfig for the kiali deployment in kubernetes #7150
Comments
@jmazzitelli Can you follow up with @ceastman-r7 and make sure we better understand the ask here? |
@ceastman-r7 what are looking for here? Is this to be an additional setting in the Kiali CR's This part of your issue description is confusing me:
|
@ceastman-r7 Can you answer the question above? |
For instance the ask is to have the ability to add a configuration so that the pod yaml looks like the following: ` |
@jmazzitelli Does that give you enough context? |
Can you reformat that :) You want triple-backticks to format in yaml. I'm guessing you want to configure this: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config |
|
This is ready for review. This new feature should be available in the next sprint release due in about 3 weeks. PRs: |
What do you want to improve?
Allow the ability to add a dnsconfig option to the deployment spec
mainly to have the following:
dnsConfig: options: - name: ndots value: "1"
What is the current behavior?
current behavior is to have ndots default to 5
From the resolv.conf man:
ndots:n
sets a threshold for the number of dots which must appear in a name before an initial absolute query will be made. The default for n is 5, meaning that if there are any dots in a name, the name will be tried first as an absolute name before any search list elements are appended to it
in aws kubernetes the typically resolv.conf is as follows:
search apps.svc.cluster.local svc.cluster.local cluster.local us-east-2.compute.internal
nameserver 172.20.0.10
options ndots:5
What is the new behavior?
All the default dnsconfig to be overridden to allow ndots: 1
The text was updated successfully, but these errors were encountered: