Ways to connect using a passed context name

[davidmichaelkarr]

I'm working on a kubectl facade for executing some common tasks in a known environment. I will need to pass in a context name on the command line and connect with that context. I noticed the following function in a type in clientcmd:

https://pkg.go.dev/k8s.io/client-go/tools/clientcmd#NewNonInteractiveDeferredLoadingClientConfig

Note the doc for this function:

"NewNonInteractiveDeferredLoadingClientConfig creates a ClientConfig using the passed context name"

Note that this function takes a ClientConfigLoader and a *ConfigOverrides . No context name there. It seems like this is a documentation bug, although note that I'm using version 0.24. I didn't check to see whether this is different in latest.

I noticed there is at least one other related function that does take a context name, although it doesn't have "DeferredLoading" in the name. I haven't looked at the code for this. What exactly does this defer the loading of? The other function(s) that take a context name didn't appear to have the "DeferredLoading" choice.

[k8s-triage-robot]

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

This bot triages un-triaged 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:

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

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

/lifecycle stale