d71829a1fc
We don't want to set the name directly because then starting the pod can fail when the node is temporarily out of resources (https://github.com/kubernetes/kubernetes/issues/87855). For CSI driver deployments, we have three options: - modify the pod spec with custom code, similar to how the NodeSelection utility code does it - add variants of SetNodeSelection and SetNodeAffinity which work with a pod spec instead of a pod - change their parameter from pod to pod spec and then use them also when patching a pod spec The last approach is used here because it seems more general. There might be other cases in the future where there's only a pod spec that needs to be modified. |
||
|---|---|---|
| .. | ||
| BUILD | ||
| create.go | ||
| deployment.go | ||
| framework.go | ||
| host_exec.go | ||
| local.go | ||
| utils.go | ||