-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs:added k3s wsl2 setup code snippet #3597
base: main
Are you sure you want to change the base?
Conversation
Hi @animeshdas2000. Thanks for your PR. I'm waiting for a jenkins-x or todo 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 jenkins-x/lighthouse repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3597 here |
The standard script used to install k3s also does not work for WSL2 as it uses systemd (which is not present in WSL2), can you update that as well? |
Sure,will add it |
Signed-off-by: Animesh Das <[email protected]>
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3597 here |
Signed-off-by: Animesh Das <[email protected]>
Signed-off-by: Animesh Das <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
⭐ PR built and available in a preview jenkins-x-jx-docs-pr-3597 here |
Please rebase this PR with the latest main branch. |
Description
As per the documentation on https://jenkins-x.io/v3/admin/platforms/k3s/#vault it wasn't possible to set up vault in k3s on WSL2 hence breaking the setup process.
Fixes # (issue)
This issue was resolved by mentioning
-p <PORT NUMBER>:<PORT NUMBER>
instead of--net host
.Checklist: