aa8927abb4
When an allocation runs for a task driver that can't support volume mounts, the mounting will fail in a way that can be hard to understand. With host volumes this usually means failing silently, whereas with CSI the operator gets inscrutable internals exposed in the `nomad alloc status`. This changeset adds a MountConfig field to the task driver Capabilities response. We validate this when the `csi_hook` or `volume_hook` fires and return a user-friendly error. Note that we don't currently have a way to get driver capabilities up to the server, except through attributes. Validating this when the user initially submits the jobspec would be even better than what we're doing here (and could be useful for all our other capabilities), but that's out of scope for this changeset. Also note that the MountConfig enum starts with "supports all" in order to support community plugins in a backwards compatible way, rather than cutting them off from volume mounting unexpectedly. |
||
|---|---|---|
| .. | ||
| interfaces | ||
| state | ||
| taskrunner | ||
| alloc_runner.go | ||
| alloc_runner_hooks.go | ||
| alloc_runner_test.go | ||
| alloc_runner_unix_test.go | ||
| allocdir_hook.go | ||
| config.go | ||
| consulsock_hook.go | ||
| consulsock_hook_test.go | ||
| csi_hook.go | ||
| groupservice_hook.go | ||
| groupservice_hook_test.go | ||
| health_hook.go | ||
| health_hook_test.go | ||
| migrate_hook.go | ||
| network_hook.go | ||
| network_hook_test.go | ||
| network_manager_linux.go | ||
| network_manager_linux_test.go | ||
| network_manager_nonlinux.go | ||
| networking.go | ||
| networking_bridge_linux.go | ||
| task_hook_coordinator.go | ||
| task_hook_coordinator_test.go | ||
| testing.go | ||
| upstream_allocs_hook.go | ||
| util.go | ||