-
Notifications
You must be signed in to change notification settings - Fork 729
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
better example for helm mountOptions #202
base: master
Are you sure you want to change the base?
Conversation
|
Welcome @TiloGit! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: TiloGit 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @TiloGit,
mountOptions
is an array.
using your solution (nfs.mountOptions={"nolock\,nfsvers=3"}
) will produce:
mountOptions:
- nolock,nfsvers=3
the correct way is to use nfs.mountOptions={"nolock"\,"nfsvers=3"}
which will produce:
mountOptions:
- nolock
- nfsvers=3
@yonatankahana good call, I updated that. |
@TiloGit can you please also bump the charts version (https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/blob/master/charts/nfs-subdir-external-provisioner/Chart.yaml#L6) to |
@@ -69,7 +69,7 @@ The following tables lists the configurable parameters of this chart and their d | |||
| `leaderElection.enabled` | Enables or disables leader election | `true` | | |||
| `nfs.server` | Hostname of the NFS server (required) | null (ip or hostname) | | |||
| `nfs.path` | Basepath of the mount point to be used | `/nfs-storage` | | |||
| `nfs.mountOptions` | Mount options (e.g. 'nfsvers=3') | null | | |||
| `nfs.mountOptions` | Mount options (e.g. {"nolock"\,"nfsvers=3"}) | null | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the \
disappears when file is rendered as you can see here: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/blob/27d772798deb510c105b05618686f35cf0cb71ec/charts/nfs-subdir-external-provisioner/README.md
you can just remove it i think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good call. needed double slash to escape.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i am wondering, the slash required only in helm --set
because helm reads the comma as a separator between variables and the slash escapes it. but in this context maybe {"nolock","nfsvers=3"}
without escape character is more fit... what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TiloGit wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the install example list example with set. ; Can this be configured somehow else?
The values possible I would get from the Parameter list so if the set requires a escape the example should have it imho.
done, do you need this also for readme changes? |
yes, even though, personally, i don't consider it a version - the github action does detects it as a change and require version bump. |
better example for mountOptions readme with current example `--set nfs.mountOptions='nfsvers=3'` I got error in helm: ```console Error: INSTALLATION FAILED: template: nfs-subdir-external-provisioner/templates/storageclass.yaml:28:19: executing "nfs-subdir-external-provisioner/templates/storageclass.yaml" at <.Values.nfs.mountOptions>: range can't iterate over nfsvers=3 helm.go:84: [debug] template: nfs-subdir-external-provisioner/templates/storageclass.yaml:28:19: executing "nfs-subdir-external-provisioner/templates/storageclass.yaml" at <.Values.nfs.mountOptions>: range can't iterate over nfsvers=3 INSTALLATION FAILED bump helm version to 4.0.17 for readme change
@yonatankahana done, thanks for being patient with me. |
@yonatankahana let me know if you need anything else from me. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@TiloGit |
This field doesn't exist... I'm editing the deployment in the nfs block and it's erroring out.
|
PR needs rebase. 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. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
with current example
--set nfs.mountOptions='nfsvers=3'
I got error in helm:this works better for me:
--set nfs.mountOptions={"nfsvers=3"}
or with other
--set nfs.mountOptions={"nolock\,nfsvers=3"}