Skip to content
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

Secret topology support #57

Closed
nightkr opened this issue Feb 15, 2022 · 0 comments
Closed

Secret topology support #57

nightkr opened this issue Feb 15, 2022 · 0 comments
Assignees

Comments

@nightkr
Copy link
Member

nightkr commented Feb 15, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant