📖 More generic explanation about issue getting kubeconfig on certain systems using Docker

[RobinDeBock]

What this PR does / why we need it:
Following the comment of @sbueringer #6595 (comment) I have updated the documentation regarding an issue when using Docker (Desktop) on macOS, or when using Docker Desktop on Linux (Docker Enginer works fine).
The documentation only mentioned the fix for Mac users, now the more generic explanation targets all the appriopriate users.

Which issue(s) this PR fixes:
The issue is already closed, but resulted from the lack of this information: #6595

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: RobinDeBock / name: Robin De Bock (16a2c91)

[k8s-ci-robot]

Welcome @RobinDeBock!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. 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/cluster-api 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. 😃

[k8s-ci-robot]

Hi @RobinDeBock. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sbueringer]

Thank you very much, a few nits

[sbueringer]

@RobinDeBock Thx can you please squash the commits?

[fabriziopandini]

/ok-to-test

[RobinDeBock]

@RobinDeBock Thx can you please squash the commits?

@sbueringer
I'm sorry, I'm new to this way of working. Could you explain how to squash commits already pushed to the remote?
I made these changes using the GitHub website and it made it into seperate commits.

[sbueringer]

@RobinDeBock Thx can you please squash the commits?

@sbueringer I'm sorry, I'm new to this way of working. Could you explain how to squash commits already pushed to the remote? I made these changes using the GitHub website and it made it into seperate commits.

I don't think you can squash via the GitHub UI, usually this is done locally via git. Do you have git setup locally and are you familiar with it?

Otherwise it might be better if I squash for you and then you can take the time to learn more about Git (if you want to)

[RobinDeBock]

@RobinDeBock Thx can you please squash the commits?

@sbueringer I'm sorry, I'm new to this way of working. Could you explain how to squash commits already pushed to the remote? I made these changes using the GitHub website and it made it into seperate commits.

I don't think you can squash via the GitHub UI, usually this is done locally via git. Do you have git setup locally and are you familiar with it?

Otherwise it might be better if I squash for you and then you can take the time to learn more about Git (if you want to)

I'm familiar with Git and got it installed locally. I just wanted to check before undoing these last commits and then squashing them, because it's quite impactful. Thanks for the suggestion though ;)

[sbueringer]

Okay good. Just asked because otherwise I would have to start somewhere else and not at "how to squash" :)

If you are on your local branch

# 5 is the number of commits you want to edit
git rebase -i HEAD~5
# An editor should open, mark commits that you want squashed as "squash"
# In your case mark every commit except the first one as squash
# then write+quit
git push --force

See: https://www.git-tower.com/learn/git/faq/git-squash (there's a gif below " If you mark one or more lines as "squash", they will be combined with the one above:")

[RobinDeBock]

@sbueringer I pushed the changes you asked for, thanks!

[sbueringer]

Thx!

/lgtm
/assign @fabriziopandini

[sbueringer]

/approve

[sbueringer]

/cherry-pick release-1.2

[k8s-infra-cherrypick-robot]

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.2 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 [sbueringer]

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

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6692

In response to this:

/cherry-pick release-1.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.