-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Unable to register the GCE persistent disk CSI Driver #7734
Comments
Hi @auto-store! The thing that immediately jumps out at me is the arguments you're passing to the plugin. If I look at the k8s jobspec it looks like it wants If that doesn't help, can you provide Nomad logs for the clients where these plugin jobs are running? Also, the allocation logs (from Also, keep in mind that right now it takes a good ~30s or so for a plugin to be registered. This is #7296 |
Thanks @tgross. So I can see the container needs service account credentials.
So now the job file looks like this:
note the endpoint is Both controller and node jobs are running and healthy, but
same for the node job. looks like it is set up and listening? here are is some log output for the node the job is running on:
|
The log from the allocation says:
So the plugin is listening on The csi_plugin {
id = "gcepd"
type = "node"
mount_dir = "/csi"
} The Nomad client logs you've provided are only the end of the log (that's the As I mentioned earlier, if I look at the k8s jobspec it looks like it wants args = [
"--csi-address=unix://csi/csi.sock",
"--v=6",
"--logtostderr",
"--run-node-service=false"
]
} |
When we exec'd into the container, the executable expects the flag to be -entrypoint. Is it possible that we are conflating GCE plugins? |
Could be. No link to the plugin was provided here so I was going from the name. Is there one other than the one in the k8s sigs org that I've linked to? |
changed to the args suggested. this is the allocation log for the controller, which is stuck in pending:
using the same link as you @tgross |
Oh yup you're right, the link I have points to the config for the "provisioner" (their non-CSI sidecar). |
We were using this container - gcr.io/gke-release/gcp-compute-persistent-disk-csi-driver:v0.7.0-gke.0 (from here. I popped into the container and ran the plugin by hand to check the flags.
Gonna try and bring up my own copy |
This will ship in the 0.11.1 release. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
0.11.0
Issue
When running the GCE Persistent disk driver as a Nomad Job, I am unable to register the CSI plugin with Nomad. Both controller and Node jobs are in a healthy state.
Job file
Controller Job spec:
Node job spec:
The text was updated successfully, but these errors were encountered: