-
Notifications
You must be signed in to change notification settings - Fork 218
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
Supports for taint
node
#564
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues 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 issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
@V2arK If the CSI driver itself is not running on the tainted node, add tolerations to its DaemonSet. Then i think it should work. |
You can use
|
Because default storge class driver for
minikube
don't supportsecureContext
, I have to use this as a storage class driver for a minikube local dev environment for a project. And to mimic the actual setup on the cloud, taint is used for compute nodes, and this resulted incsi-hostpath-driver
not allocating PVCs on compute node at all.Right now I have to tolerate the taints and make the related daemonset / statefulset / deployment runs only on the tainted node to force the system to allocate PVCs on the tainted node.
Some support for this is needed.
The text was updated successfully, but these errors were encountered: