Need a way to get kubeconfig with node IP

[BenTheElder]

What would you like to be added:
Some way to get the kubeconfig with the server field using the node container IP rather than the port forward on the hosts loopback or the internal DNS.

Why is this needed:

You could do this in 0.7 and on Linux it works from both host and inside the node / pods

[howardjohn]

kind get kubeconfig --name "${CLUSTER_NAME}" --internal | sed "s/${CLUSTER_NAME}-control-plane/$(docker inspect "${CLUSTER_NAME}-control-plane" --format "{{ .NetworkSettings.Networks.kind.IPAddress }}")/g"

Is a workaround

[aojea]

/assign

[aojea]

/close
I can't see now the utility of having the ip, there are multiple ways to obtain it,

• kubectl get nodes
• nslookup

[k8s-ci-robot]

@aojea: Closing this issue.

In response to this:

/close
I can't see now the utility of having the ip, there are multiple ways to obtain it,

• kubectl get nodes
• nslookup

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.

[howardjohn]

The utility is that you can use the kubeconfig from within docker. Common in multicluster. Getting the IP is not so hard, but having to sed patch it isn't ideal

[aojea]

kubectl get nodes -o=jsonpath='{range .items[*]}{.metadata.name}{":"}{.status.addresses[?(@.type=="InternalIP")].address}{"\n"}{end}'
testapi-control-plane:172.19.0.6
testapi-control-plane2:172.19.0.5
testapi-control-plane3:172.19.0.4

[aojea]

is not valid using kubectl directly?

[BenTheElder]

/assign

[MadhavJivrajani]

/remove-kind design
/kind feature
kind/design is migrated to kind/feature, see kubernetes/community#6144 for more details