docs: describe how to use podman with kind #202
Conversation
The committers listed above are authorized under a signed CLA. |
|
Welcome @sudomateo! |
|
Hi @sudomateo. 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 Once the patch is verified, the new status will be reflected by the 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-sigs/prow repository. |
| running as root, which is not recommended. | ||
|
|
||
| To connect to your service when using Podman, run `cloud-provider-kind` with the | ||
| `-enable-lb-port-mapping` option. This configures the Envoy container with an |
There was a problem hiding this comment.
| `-enable-lb-port-mapping` option. This configures the Envoy container with an | |
| `--enable-lb-port-mapping` option. This configures the Envoy container with an |
There was a problem hiding this comment.
The --help option lists the options with a single dash. That's the only reason I used it that way. Happy to change though.
> cloud-provider-kind --help
Usage: cloud-provider-kind [options]
-enable-lb-port-mapping
enable port-mapping on the load balancer ports
-enable-log-dumping
store logs to a temporal directory or to the directory specified using the logs-dir flag
-logs-dir string
store logs to the specified directory
-v int
Verbosity level (default 2)
I'm fine with signing a CLA but I don't feel comfortable listing my address in the Docusign when I don't know who has access to it. This is a documentation contribution, not code. I'm happy to relinquish whatever rights so that the
|
I don't really know how this work, AFAIK these are Linux Foundation policies ... I really don't know what fields are mandatory and what are optional, maybe you can skip filling in those? |
This patch adds a section to the README describing how to use Podman with `cloud-provider-kind`. Podman does not allow sharing the host networking or binding to privileged ports so the `-enable-lb-port-mapping` option can be used to get an ephemeral port on the host that maps to the `LoadBalancer` listening port.
0f17d76 to
f7f01bf
Compare
I used |
|
/ok-to-test defer LGTM to @stmcginnis Thanks |
|
The CNCF runs the CLA system and ultimately owns the copyright, trademarks etc, so we're just required to use it for kubernetes repos. (Some newer CNCF projects use DCO, but not the Kubernetes org). FWIW they do have a help desk listed here: https://github.com/cncf/cla#troubleshooting |
|
AFAIK, the database is private to the linux foundation and nobody in the Kubernetes project can see it (not even the steering committee), my understanding is that it exists so CNCF/LF legal can reach out if needed, but I don't know who exactly has access. @jeefy is this documented anywhere? |
|
let's merge, this is very useful documentation as it is a very hard to explain feature |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, sudomateo 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:
Approvers can indicate their approval by writing |
This patch adds a section to the README describing how to use Podman with
cloud-provider-kind. Podman does not allow sharing the host networking or binding to privileged ports so the-enable-lb-port-mappingoption can be used to get an ephemeral port on the host that maps to theLoadBalancerlistening port.