add APIServer endpoint to minikube profile list

[balopat]

For Skaffold (GoogleContainerTools/skaffold#3668) we know the current context. That context has an API server endpoint:

- cluster:
    certificate-authority: /Users/.../.minikube/ca.crt
    server: https://127.0.0.1:32777
  name: docker3

I want to be able to join my API Server endpoint to a minikube profile.

Currently this is not possible for the Docker driver, as the Node spec contains the node IP not the API Server endpoint:

....
 "Nodes": [
          {
            "Name": "docker3",
            "IP": "172.17.0.4",
            "Port": 8443,
            "KubernetesVersion": "v1.17.2",
            "ControlPlane": true,
            "Worker": true
          }
...

Can we add a cluster-wide property, APIServer to the json listing?

[medyagh]

@balopat that is a good idea ! we could add a field,
"ApiserverEndpoint"
in VM world they used to be the same, but in docker/podman driver it is a different story.

We could do that.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[sharifelgamal]

/lifecycle frozen

[tharun208]

@medyagh , I like to work on this

[briandealwis]

An alternative is to add the profile name to the context and cluster extensions as Minikube is now doing with cluster_info:

- cluster:
    certificate-authority: /Users/bdealwis/.minikube/ca.crt
    extensions:
    - extension:
        last-update: Mon, 22 Mar 2021 21:45:57 EDT
        provider: minikube.sigs.k8s.io
        version: v1.18.1
      name: cluster_info
    server: https://127.0.0.1:61837
  name: containerd

Then the minikube instance could remain blissfully ignorant of how its endpoints are exposed to the host environment.