kubernetes/minikube

Host DNS search domain is not propagated to minikube DNS

Open

#1,676 opened on 2017年7月5日

GitHub で見る
 (10 comments) (15 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
area/dnshelp wantedkind/featurelifecycle/frozenpriority/backlogr/2019q2

説明

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Minikube version (use minikube version): v0.20.0

Environment:

  • OS (e.g. from /etc/os-release): Windows 7
  • VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualbox
  • ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): file://C:/cygwin64/home/b26978/.minikube/cache/iso/minikube-v0.20.0.iso
  • Install tools:
  • Others:

What happened: When I create a new minikube using minikube start the DNS configuration inside the minikube VM doesn't use the same DNS search domain as the host uses. I'm behind a corporate firewall and the proxy hostname isn't resolvable from inside the VM, thus the http_proxy and https_proxy settings are useless.

Apparently the DNS system is managed by systemd-resolved, and the configuration file at used is located at: /etc/systemd/resolved.conf. The Domains settings inside is commented in my configuration. I managed to get the DNS (and proxy) working by setting the Domains value in the /etc/systemd/resolved.conf and restarting the service:

systemctl daemon-reload
systemctl restart systemd-resolved

Sadly, I'm not fluent in Go and I'm not able to submit a patch to fix the issue.

What you expected to happen: The configuration file (/etc/systemd/resolved.conf) contains the Domains settings and it's set to the correct value.

How to reproduce it (as minimally and precisely as possible): Set the DNS domain search to something (non empty) under Windows 7. Create a new minikube vm using minikube start.

Anything else do we need to know:

コントリビューターガイド

技術スタック
goshell
領域
backendinfrastructure
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Basic Go knowledgeUnderstanding of DNS configurationFamiliarity with systemdMinikube architecture
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
45
調査方針
Investigate how minikube configures DNS inside the VM, likely in the driver or provisioning code (e.g., pkg/minikube/cluster/cluster.go, pkg/minikube/drivers/virtualbox.go). Look for where /etc/systemd/resolved.conf is set or where DNS servers are applied. The goal is to propagate the host's DNS search domain to the VM's systemd resolved configuration. Check existing discussions in the issue comments for any pointers or partial solutions.