Skip to content
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

Mismatch of documentation between operation and HELM chart #329

Open
AssafKatz3 opened this issue Jul 20, 2022 · 6 comments
Open

Mismatch of documentation between operation and HELM chart #329

AssafKatz3 opened this issue Jul 20, 2022 · 6 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@AssafKatz3
Copy link

Hi,
Operations mention discovery directory but helm documentation doesn't refer to it at all.
Therefore it isn't clear how should I configure the HELM chart for the case of Sharing a disk filesystem by multiple filesystem PVs
.
Thanks

@mauriciopoppe
Copy link
Member

The setup is a 2 step process for the case "Sharing a disk filesystem by multiple filesystem PVs"

  1. Do the setup described in Sharing a disk filesystem by multiple filesystem PVs, this setup is typically done when the node is bootstrapped
  2. As you can see in the commands there are n mount points created in /mnt/disks therefore the discovery directory is /mnt/disks. Next install the helm chart with a class that uses this discovery directory e.g. https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/helm/examples/development-gke.yaml. In the README search for the options that start with classes.[n] too.

@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 18, 2022
@mauriciopoppe
Copy link
Member

/remove-lifecycle stale

I think we could add a reference from the helm docs to the operations docs for the glossary among other things.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2022
@mauriciopoppe mauriciopoppe added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 19, 2022
@Kartik494
Copy link
Contributor

I would like to give a try on this.
/assign

@AssafKatz3
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

5 participants