Fix getting the current cluster name in README.md

[pierreis]

The current documentation suggests using the current context name (provided by kubectl config current-context) as cluster name.

This does not work in configurations in which there is a mismatch between the cluster and context name (_e.g., K8s provided by Docker for Mac).

This pull request fixes this by using the output of kubectl config view --minify -o=jsonpath='{.contexts[0].context.cluster}' instead.

Fixes #213

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[pierreis]

/assign @fejta

[googlebot]

CLAs look good, thanks!

[fejta]

@nlopezgi
Context is the combination of user + cluster. By default gcloud will set user, cluster and context to be the same thing (probably why this bug exists) but that need not be the case. Totally possible that other distros besides GKE do something different.

Context may actually be what most people want here (and is typically what people use). Probably worth providing a context parameter here in addition to cluster (which is probably better than repurposing cluster to be cluster).

@mattmoor can you comment on the history here? Is this an accident or intentional?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fejta

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 [fejta]

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

[fejta]

/ok-to-test

[fejta]

/retest

[fejta]

/retest

[fejta]

/assign @smukherj1

Any idea why this keeps failing? Are we out of quota?

[fejta]

/retest

[fejta]

Also @smukherj1 @nlopezgi can you trigger the non prow builds?

[smukherj1]

Opened #216 to hopefully reduce e2e flakiness