-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Closed
Labels
addon/storage-provisionerIssues relating to storage provisioner addonIssues relating to storage provisioner addonco/multinodeIssues related to multinode clustersIssues related to multinode clustershelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.
Description
It seems that the hostpath provisioner is completely unsuitable for multinode installations.
It must create and prepare directories on the exact host on which a pv is requested. In addition, it must add nodeaffinity for every hostpath pv exactly the same as it happens at https://github.com/rancher/local-path-provisioner
Steps to reproduce the issue:
- minikube create -n 3
- install any statefulset that requests pv and has pod anti affinity rule
minikube version: v1.22.0
storage-provisioner: image: 'gcr.io/k8s-minikube/storage-provisioner:v5'
R-omk
Metadata
Metadata
Assignees
Labels
addon/storage-provisionerIssues relating to storage provisioner addonIssues relating to storage provisioner addonco/multinodeIssues related to multinode clustersIssues related to multinode clustershelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.