✨ add GetConfigWithContext to retrieve a config with a specific context

[sbueringer]

This PR adds a new function to the config package. Before it was only possible to retrieve the current context of a kubeconfig file via GetConfig. Now there's an additional GetConfigWithContext where a specific context can be retrieved.

The advantage is when developing locally (run controllers via IDE) with a specified context, the controller is not dependent on whatever the current context is of the used kubeconfig file.

Fixes #479

[k8s-ci-robot]

Welcome @sbueringer!

It looks like this is your first PR to kubernetes-sigs/controller-runtime 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/controller-runtime has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[sbueringer]

/assign @DirectXMan12

[sbueringer]

@DirectXMan12 How do I fix the following build error? Couldn't find anything in the docs. dep ensure changes a lot in Gpkg.lock, go.mod & go.sum.

k8s.io/client-go/tools/clientcmd/api: imported or required, but missing from Gopkg.lock's input-imports
The command "GO111MODULE=on TRACE=1 ./hack/check-everything.sh" exited with 1.

EDIT: okay I fixed it by adding the line manually to Gopkg.locks then I tried hack/check-everything.sh and it worked (but it also lead to changes in go.mod & go.sum which I didn't checked in). What would have been the right/automated way to fix it?

[DirectXMan12]

dep ensure --no-vendor should fix dep, and go mod tidy should fix go.mod.

[DirectXMan12]

Can you add a bit more details to the PR message beyond just the fixes? It's useful when going through with git log.

[DirectXMan12]

otherwise looks reasonable

[sbueringer]

Can you add a bit more details to the PR message beyond just the fixes? It's useful when going through with git log.

I added some more text here in the PR. The commit message itself already is: add GetConfigWithContext to retrieve a config with a specific context. Do I have to squash the fix gopkg check commit by myself or is that done by the automation?

EDIT: I squashed the commit by myself, but just out of curiosity for the next time. Is it done automatically?

[DirectXMan12]

We don't automatically squash, no. It's up to the submitter to produce a chain of logical commits (we don't enforce 1 commit per PR -- we just prefer that each commit stands on its own).

[DirectXMan12]

/lgtm
/approve

thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DirectXMan12, sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [DirectXMan12]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment