agent-substrate / agent-substrate/substrate
Atelet should only run on nodes where ateoms are running.
Abierto
area/node
area/scheduling
kind/feature
prio/P1
- Lenguaje dominante
- Go
- Estrellas
- 1.8k
- Forks
- 316
- Merge medio
- 2 d 43 min
- PR fusionados (30 d)
- 287
Descripción
Today, atelet is deployed as a DaemonSet, which means it runs on all nodes in the cluster, taking into account taints and tolerations.
Ateom pods are managed as Deployments today, though we may eventually switch to a custom workload controller.
We should find a solution that places atelet pods only on nodes where ateoms are or will be running.
This could look like:
* Manage atelets from the same workload controller as ateoms, so that it can place atelet pods on the correct nodes
* Come up with a convention for tainting certain nodes as only for ateoms, not regular workloads.
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.