BC brake compatebility in /etc/hosts

[wirwolf]

Hello, community. I want discuss this fix https://github.com/kubernetes-sigs/kubespray/pull/7634 because after these changes i damage my cluster.

I have some DNS structure

node1.prod.mydomain.org
node2.prod.mydomain.org
node3.prod.mydomain.org
rabbitmq.prod.mydomain.org

I use kubespray 2.18 for build my cluster my inventory.ini is

[all]
node1.prod.mydomain.org ansible_host=***** ip=*******
node2.prod.mydomain.org ansible_host=***** ip=*******
node3.prod.mydomain.org ansible_host=***** ip=*******
node4.prod.mydomain.org ansible_host=***** ip=*******

[kube_control_plane]
node1.prod.mydomain.org
node2.prod.mydomain.org
node3.prod.mydomain.org

[etcd]
node1.prod.mydomain.org

[kube_node]
node2.prod.mydomain.org
node3.prod.mydomain.org
node4.prod.mydomain.org

[calico_rr]

[prod_cluster:children]
kube_control_plane
kube_node
calico_rr

and variable cluster_name: k8s.prod.mydomain.org

And all work fine. Internal DNS Kubernetes work in k8s.prod.mydomain.org and when i want to connect to an external service DNS resolve external IP rabbitmq.prod.mydomain.org and all work correct.

When i update my cluster from 1.21.7 to 1.21.13 using master branch (last commit https://github.com/kubernetes-sigs/kubespray/commit/14acd124bc0c326b4149c767c26ea0311d725074) i have some problems because internal name removed from host file and when i run kubectl log -f <pod-id> i see error

Failed to load logs: Get "https://node1.prod.mydomain.org:10250/containerLogs/kube-system/etcd-node1.prod.mydomain.org/etcd?tailLines=502&timestamps=true": dial tcp 127.0.1.1:10250: connect: connection refused
Reason: undefined (500)

Resolution: I propouse add flag for adding all host names to hosts file

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[wirwolf]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.