Summary
The user discusses managing agents in multi-cluster deployments, questioning the necessity of replicating a config map. They mention that while the Flyte config system can handle multiple configurations, the current Propeller version does not automatically reload the config. The user describes their setup with multiple data centers and Kubernetes clusters, noting that Flyte control and data plane configurations are already replicated across all clusters. They emphasize that each Propeller instance only loads and merges config maps within its own cluster.
shuliang
exactly.
kumare
but this is just deployment so its ok
kumare
ya that is fine, what i meant was, that if you have a central control plane
shuliang
We have multiple datacenter in each region, in each data center, there are multiple k8s clusters. Currently with or without agents, the flyte control plane and data plane configuration are replicated in each k8s cluster in each datacenter. The replication of the config already happens for every cluster even without custom agents configuration. The point is that each propeller just load/merges the configmaps in the same cluster.
kumare
I like the idea of managing agents externally- cc <@UNW4VP36V> Just a question in multi cluster deployments we will have to replicate this config map everywhere
Flyte config system can handle multiple configs, but currently propeller does not auto reload the config (this is possible)