"node affinity conflict" following Deployment instructions in README about csi-driver-host-path HOT 22 CLOSED

The 1.16 deployment is not meant to work with 1.13 because it uses newer Kubernetes features. Try using a 1.13 deployment spec from an older release

from csi-driver-host-path.

@msau42 Why do you think I'm using 1.13, Michelle? It's 1.16

: csi-driver-host-path 227;  kcf version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
: csi-driver-host-path 228;  alias kcf
alias kcf='KUBECONFIG=~/fedora1.kubeconfig kubectl'

from csi-driver-host-path.

Oh sorry, I misread your original comment about replacing 1.13. Can you check your kubelet logs for hints to driver registration? It is kubelet that is supposed to create the CSINode object. And make sure that the CSINodeInfo feature gate is enabled on your cluster (all components, apiserver, scheduler, kubelet, kube-controller-manager, etc)

from csi-driver-host-path.

Thank you for clarifying the answer to "What creates the CSINode object?".
At https://kubernetes-csi.github.io/docs/csi-node-object.html I read
"In Kubernetes v1.12 and v1.13, because the feature was alpha, it was disabled by default."
so I understood that the --feature-gate was unnecessary for 1.16.
However, I added it anyway to the files

/var/snap/microk8s/current/args/kube-apiserver
/var/snap/microk8s/current/args/kube-controller-manager
/var/snap/microk8s/current/args/kubelet
/var/snap/microk8s/current/args/kube-proxy
/var/snap/microk8s/current/args/kube-scheduler

and restarted microk8s.
I verified with 'ps aux' that it had been passed to the kube* commands, but the problem was unchanged.

I did

journalctl |grep kubelet|tail

and saw nothing added to it when I repeated the

kubectl apply -f ./examples/csi-app.yaml

(The lines at the end are "Image garbage collection failed" messages - the disk is at 92%.)

I also found the gocsi tool to see what that would say

: args 117;  sudo ~/go/src/gocsi/csc/csc node get-info --endpoint /var/lib/kubelet/plugins/csi-hostpath/csi.sock
localhost.localdomain	0	&csi.Topology{Segments:map[string]string{"topology.hostpath.csi/node":"localhost.localdomain"}, XXX_NoUnkeyedLiteral:struct {}{}, XXX_unrecognized:[]uint8(nil), XXX_sizecache:0}

but kubectl get csinode still outputs No resources found.

Thanks for responding. I'm still assuming the absence of the CSINode is the cause of the problem. I will get back to this tomorrow and try again to see if there is something I've missed.

from csi-driver-host-path.

The driver registration should happen as part of ./deploy-hostpath.sh.

Can you check that "/var/lib/kubelet" is configured as the kubelet's root in microk8s? If not, then the hostpath deployment spec should replace all instances of "/var/lib/kubelet" with whatever your kubelet root is.

from csi-driver-host-path.

The CSINodeInfo feature gate should be enabled by default starting in 1.14.

from csi-driver-host-path.

That was inspired, Michelle.

pgrep -a kubelet|sed -n 's@.*\(--root-dir=[^ ]*\).*@\1@p' # output:
--root-dir=/var/snap/microk8s/common/var/lib/kubelet

I decided the simplest way to resolve that was to do

cd /var/lib
sudo mv kubelet/ kubelet.org
sudo ln -s /var/snap/microk8s/common/var/lib/kubelet/

And all was well.

I've closed a pull request because I don't have time for the "new contibutor"/corporate process now. You can amend the documentation or not as you wish.

Update: If might renew the pull request next week if I get a chance (and this hasn't been closed already). Thanks again.

from csi-driver-host-path.

Sorry, but it's already apparent that I won't get contributor approval through my current employer. I suggest you add a brief note to the README.md and this can be closed.

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

Formally, this can be fixed by adding a short note to the README.

However, what would be much better would be for the kubelet root dir to be made available symbolically so that any yaml that needs to refer to it could do so indirectly and remain independent of the actual value. If that were done, there would be no dependency on the kubernetes config options or distribution - it would even be possible to deploy drivers like this where some nodes had kubelet running with a different root-dir to other nodes.

/remove-lifecycle stale

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

/remove-lifecycle stale

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

/remove-lifecycle stale

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

The ask here is to document the steps needed to deploy the driver when the kubelet root directory is not "/var/lib/kubelet". Maybe we could actually take it a step further and make it customizable in the deployment script.

/help
/remove-lifecycle stale

from csi-driver-host-path.

@msau42:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

from csi-driver-host-path.

/remove-lifecycle rotten

from csi-driver-host-path.

Issue #71 is an older issue about the same problem. Let's treat this one here as a duplicate and close it.

/close

from csi-driver-host-path.

@pohly: Closing this issue.

from csi-driver-host-path.