Skip to content

update README.md to match the current config #33

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 11, 2025
Merged

update README.md to match the current config #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ To deploy this component, its basically a 2 step process

You would want to create the vcluster with the following `values.yaml`:
```
syncer:
extraArgs:
- --mount-physical-host-paths=true
controlPlane:
hostPathMapper:
enabled: true
```

* For new vcluster run `vcluster create <vcluster_name> -f values.yaml`
Expand All @@ -24,8 +24,7 @@ Now that the vcluster itself is ready, we can deploy the hostpath mapper compone
To sum up, if your vcluster is named `my-vcluster` and is deployed in namespace `my-namespace` then you should run
```shell
helm install vcluster-hpm vcluster-hpm \
--devel \ # since we currently only have a beta release
--repo https://charts.loft.sh \ # once we publish a GA chart this would not be needed
--repo https://charts.loft.sh \
-n my-namespace \
--set VclusterReleaseName=my-vcluster
```
Expand Down