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
Internally, armada supports creation of queues with namespaces.
This work would be necessary for any production usage of Armada as users will probably not submit Jobs/Pods to the default namespace
Design is needed as we will not take the armada-namespaces code in GR and migrate to OSS.
Support CRDs
Request from Bloomberg to support CRD (any general kubernetes object)
Initial ideas could be PyTorchJob, MPIJob, SparkJob, etc
General design to incorporate arbitrary objects (MCAD actually provides a way to do this)
Cloud aware and availability zone aware
One request was to only allow certain jobs to run in clusters in a certain AZ
A Banking customer said they had interest in running CronJobs accros multiple clusters but would only want certain jobs to run on cluster if it was legally allowed to run in that AZ
Argo workflow as a workflow API
Albin suggested the idea of using the dag syntax for argo
We would build our own runner but we could support a CNCF dag language in our API so we can start supporting dags more directly
Currently GR has a myriad of dags spread across the entire repo
Argo has a proto api that definies their API so we could import that in our code.
Google engineers mentioned the idea of providing manpower for support Kueue in Armada
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Batch Community Ideas
Improve scalability of ETCD
Start discussions about standardizing on a queue api definition for various CNCF projects
Armada Feature Ideas
Beta Was this translation helpful? Give feedback.
All reactions