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
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?
Coreflux Broker
Coreflux Hub
Flux Assets
Flux Language
Power Ups
User Experience (UX)
Documentation
Conceptual Features
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
The text was updated successfully, but these errors were encountered:
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...
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.
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
The text was updated successfully, but these errors were encountered: