search

CorefluxCommunity / Coreflux-roadmap

Welcome to the Public Roadmap for Coreflux! We welcome your creativity and passion for IOT!
4 stars 0 forks source link

[Feature]: Kubernetes Orchestrator #17

Open nunocgoncalves opened 8 months ago

nunocgoncalves commented 8 months ago

Tell us about your request

A Kubernetes client integrating with the broker to simplify triggering event-driven workloads on K8s. Advantageous in ML Ops amongst many other use cases.

Which component(s) is this request for?

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Easy and flexible configuration of event-driven K8s orchestration with the Flux language.

Describe alternatives you've considered

No response

Is this request for a new asset?

No response

Additional context

No response

HugoAVaz commented 8 months ago

This was already discussed. Question - should this be handled like a Flux asset. Should the pods appear like flux assets, change restart policy , start , stop ,install , uninstall...

Or we need to add other functionality?

nunocgoncalves commented 8 months ago

The most important requirement would be a way to schedule pods (whether for creation or deletion) based on MQTT messages. Having the ability to use a K8s manifest would be ideal.