ChromeOS needs KubeletInUserNamespace

[dex4er]

I can run KIND cluster in ChromeOS sucesfully with this instruction. Actually it is not a specific to ChromeOS but it will be the same for running KIND in just any LXC container.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: dex4er / name: Piotr Roszatycki (468b9aa)

[k8s-ci-robot]

Welcome @dex4er!

It looks like this is your first PR to kubernetes-sigs/kind 🎉. 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/kind 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 @dex4er. 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.

[aojea]

/ok-to-test

[stmcginnis]

/lgtm

I have not tested and do not have a way to easily do so, but it looks like everything necessary is added and if the submitter has tested and it works for them, that's good enough for me.

One caveat I'm thinking here - should we have a statement in the docs that this is an experimental or "unsupported" use case? Great that this works and is an option for folks, but I think it strays a little outside the primary scope of the project.

In other words, it might be good to make it clear that the maintainers won't spend a lot of time troubleshooting if a user files an issue having a problem running on ChromeOS.

[BenTheElder]

/lgtm
/approve
Thank you!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, dex4er

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

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

[BenTheElder]

That's a good point @stmcginnis but we're also not currently requiring that for say, https://kind.sigs.k8s.io/docs/user/using-wsl2/ even though those docs are entirely user-contributed and not something we test (#1529). Docker Desktop on macOS is in a similar state currently as well of supported-but-not-actively-tested and only best-effort back and forth debugging via github.

[dex4er]

I see the difference between "unsupported" and "not working". I can thank you that you added the description of how to start KIND in LXC or ChromeOS even if I don't expect you can't troubleshoot such a setup.