You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the pod is first scheduled by K8s, and then we try to resolve all secrets. For statically provisioned secrets (k8sSearch) this assumes that all secrets have provisioned variants for all nodes.
Kubernetes allows CSI plugins to influence how pods using them are scheduled (https://kubernetes-csi.github.io/docs/topology.html). We should use that to nudge Kubernetes towards scheduling to nodes where those secrets are available.
The text was updated successfully, but these errors were encountered:
Currently, the pod is first scheduled by K8s, and then we try to resolve all secrets. For statically provisioned secrets (
k8sSearch
) this assumes that all secrets have provisioned variants for all nodes.Kubernetes allows CSI plugins to influence how pods using them are scheduled (https://kubernetes-csi.github.io/docs/topology.html). We should use that to nudge Kubernetes towards scheduling to nodes where those secrets are available.
The text was updated successfully, but these errors were encountered: