Skip to content

Commit

Permalink
Merge pull request #2921 from bornaivankovic/main
Browse files Browse the repository at this point in the history
doc: alternative for port mapping or ingress
  • Loading branch information
BenTheElder authored Sep 22, 2022
2 parents 1c1545b + f7bf5c6 commit 389e2be
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions site/content/docs/user/using-wsl2.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,8 @@ nodes:
1. create service `kubectl create service nodeport nginx --tcp=80:80 --node-port=30000`
1. access service `curl localhost:30000`

Alternatively, see [Helpful Tips for WSL2](#helpful-tips-for-wsl2)

## Kubernetes Service with Session Affinity

If you want to create a Kubernetes Service with `sessionAffinity: ClientIP` it will not be accessible (and neither will any Service created afterwards).
Expand Down Expand Up @@ -130,3 +132,4 @@ kernel=c:\\path\\to\\your\\kernel\\bzImage
- If you want to terminate the WSL2 instance to save memory or "reboot", open an admin PowerShell prompt and run `wsl --terminate <distro>`. Closing a WSL2 window doesn't shut it down automatically.
- You can check the status of all installed distros with `wsl --list --verbose`.
- If you had a distro installed with WSL1, you can convert it to WSL2 with `wsl --set-version <distro> 2`
- Alternative of [Accessing a Kubernetes Service running in WSL2](#accessing-a-kubernetes-service-running-in-wsl2) or [Setting Up An Ingress Controller](/docs/user/ingress/#setting-up-an-ingress-controller) for accessing workloads is using `kubectl port-forward --address=0.0.0.0`.

0 comments on commit 389e2be

Please sign in to comment.