📖 book: document how to use Lima on macOS for development

[chrischdi]

What this PR does / why we need it:

I'm using this setup for a while now and did not hit any issues. It is even more stable for me compared to docker desktop on OSX.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/area documentation

[sbueringer]

Thank you very much!

/lgtm

/assign @fabriziopandini

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c5d2d0b150ae4002544a4ba701066a7ec2089748

[chrischdi]

Thank you very much!

/lgtm

missed to add 1 parameter :-)

[sbueringer]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c24ca8c8e72326dd3060a7c87c72bd398919043d

[fabriziopandini]

Nice!

I was wondering if there is a place with higher visibility then the clusterctl documentation

I think I would prefer moving it after https://cluster-api.sigs.k8s.io/developer/tilt.html?highlight=docker#using-podman (but I also don't have strong preferences on what is the best location)

Additionally, we should probably quote that lima is a viable option in a few places

• https://cluster-api.sigs.k8s.io/developer/guide.html?highlight=docker#docker
• https://cluster-api.sigs.k8s.io/developer/tilt.html?highlight=docker#prerequisites
• https://cluster-api.sigs.k8s.io/user/quick-start.html?highlight=docker#common-prerequisites

[chrischdi]

Nice!

I was wondering if there is a place with higher visibility then the clusterctl documentation

I think I would prefer moving it after cluster-api.sigs.k8s.io/developer/tilt.html?highlight=docker#using-podman (but I also don't have strong preferences on what is the best location)

Additionally, we should probably quote that lima is a viable option in a few places

• cluster-api.sigs.k8s.io/developer/guide.html?highlight=docker#docker
• cluster-api.sigs.k8s.io/developer/tilt.html?highlight=docker#prerequisites
• cluster-api.sigs.k8s.io/user/quick-start.html?highlight=docker#common-prerequisites

Added at the first two places. At the end it is still docker which is provided via lima so it felt a bit wrong to me at the quick-start level.

But I can adjust there too if you want to.

[fabriziopandini]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 72d5a087f916f034c4c5df1c32977996ecff53d4

[sbueringer]

Last nits from my side

[fabriziopandini]

/lgtm
/approve

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

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

In response to this:

/lgtm
/approve

/cherry-pick release-1.8

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-sigs/prow repository.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a37d0ba3ec89310e8d4f07b7680cddfd86c9e135

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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

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]

@fabriziopandini: new pull request created: #11139

In response to this:

/lgtm
/approve

/cherry-pick release-1.8

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-sigs/prow repository.