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
Invoke can be run as individual swarm of headless servers using kubernetes. It would be interesting and super useful to be able for the installer/client to connect to those servers as if they were workers pools.
At first, just be able to add them manually through the Queue interface/api would be nice.
Then be able to just launch a client interface that detect them automatically (doable with the discovery capabilities of k8s) would be awesome as it would allow to get a really small client flavor that remotely connect to the cluster.
Alternatives
Spawn multiple instances on k8s and then have a custom interface that send requests to those instances API directly.
Additional Content
Here is quick UI suggestion, it would need a tab for the workers inventory list with labels and filters, but I think you get where I'm heading.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Contact Details
Fl1nt (Discord)
What should this feature add?
Invoke can be run as individual swarm of headless servers using kubernetes. It would be interesting and super useful to be able for the installer/client to connect to those servers as if they were workers pools.
At first, just be able to add them manually through the Queue interface/api would be nice.
Then be able to just launch a client interface that detect them automatically (doable with the discovery capabilities of k8s) would be awesome as it would allow to get a really small client flavor that remotely connect to the cluster.
Alternatives
Spawn multiple instances on k8s and then have a custom interface that send requests to those instances API directly.
Additional Content
Here is quick UI suggestion, it would need a tab for the workers inventory list with labels and filters, but I think you get where I'm heading.
The text was updated successfully, but these errors were encountered: