Open hongchaodeng opened 5 years ago
The main question I have is whether we should make this a core feature of Hydra, in which case it will be a core.hydra.io
. Otherwise, yes, it should go in the ext
namespace and be put in that subdirectory.
If you want to get started, go ahead and model it as extended. We can solicit feedback from the other Hydra implementors.
+1 on starting it as an ext.
Currently, we have defined Service workload for stateless, cattle-like applications. However, we have user scenarios to support stateful, pet-like applications. It would be better to define these two types of workload separately than making "stateful" a special trait of Service.
We would want to add an extended workload called StatefulService that supports stateful workload best. Initially, we can model that around k8s StatefulSet which our motivation comes from.
The StatefulService Component+Workload will be added in a new directory
extended/workload/
. Does that sound right?