what is the difference between Config.proxy_url and ExecAuthCluster.proxy_url and Cluster.proxy_url ?

[Masber]

What is the difference between:

• https://docs.rs/kube-client/1.1.0/kube_client/struct.Config.html#structfield.proxy_url
• https://docs.rs/kube-client/1.1.0/kube_client/config/struct.ExecAuthCluster.html#structfield.proxy_url
• https://docs.rs/kube-client/1.1.0/kube_client/config/struct.Cluster.html#structfield.proxy_url

How do I know which one to use when?

[clux]

well, it depends on where you are coming from.

The proxy_url in our Config is ultimately the one being used in our Client, and if you are passing these manually, it's probably the one you want to use unless you have a highly specific use case.

The one in the Cluster struct is from the upstream cluster struct that is re-used in a few places. It's the struct you find inlined in a Kubeconfig in various places.

The Exec one is specific to a specific authentication setup if you have exec stuff in your cluster config. typically you would never fill in this field yourself anywhere, but you'd deserialize the Kubeconfig and then tell kube to use that. This one should only be relevant for out-of-cluster (local) authentication with kubectl, and we use the exec settings to authenticate with a shellout to whatever's in the kubeconfig to authenticate. the specifics about this exec is in auth client mod and i'm not sure we even support proxy urls there - nor how it even makes sense tbh - my guess is upstream is just re-using the cluster struct and this is what we have imported.

There is also some upstream documentation on it.