Skip to content

salt: Remove hardcoded mentions of "cluster.local" #3468

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

Draft
wants to merge 2 commits into
base: development/2.11
Choose a base branch
from

Conversation

gdemonet
Copy link
Contributor

This domain/zone is merely a default, and should not be hardcoded
everywhere across our codebase, even though it is not configurable
today.
For now, we leave its value under coredns settings, although it should
likely live under the kubernetes key.

(we also completely remove it when referring to Loki service in the
Grafana datasource definition - which we didn't do in the ExternalName
services, though I'm not sure about that part)

gdemonet added 2 commits July 29, 2021 14:13
This domain/zone is merely a default, and should not be hardcoded
everywhere across our codebase, even though it is not configurable
today.
For now, we leave its value under `coredns` settings, although it should
likely live under the `kubernetes` key.
Relying on search domains for DNS resolution is the standard practice in
K8s, so we don't have to store the cluster domain in there. We also
remove the `.svc` part, as this is also part of the search domains.
@gdemonet gdemonet added the topic:networking Networking-related issues label Jul 29, 2021
@gdemonet gdemonet requested review from NicolasT and a team July 29, 2021 16:45
@bert-e
Copy link
Contributor

bert-e commented Jul 29, 2021

Hello gdemonet,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jul 29, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic:networking Networking-related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants