spec icon indicating copy to clipboard operation
spec copied to clipboard

Add ComponentInstance CRD

Open hongchaodeng opened this issue 6 years ago • 4 comments

Current we have a Component Schema CRD. But when we actually instantiate a component, we would need to expose its status, dependency status here. Additionally, we would need to reference this instance as a dependency for another component/instance.

This is also discussed in https://github.com/microsoft/scylla/pull/71. But it didn't exist in the spec repo.

hongchaodeng avatar Aug 15 '19 06:08 hongchaodeng

Interesting idea. My intention with implementing ComponentInstance in Kubernetes was not to introduce a new spec item, but just to give an accounting object to Kubernetes users. What implications would this have for a non-Kubernetes implementation of Hydra?

technosophos avatar Aug 15 '19 15:08 technosophos

Anyone working on a non-Kubernetes implementation, can you weigh in on this?

technosophos avatar Aug 27 '19 23:08 technosophos

@technosophos For non-K8s implementation in our side, a common use case is accounting cloud resources referenced by this application.

I think this obj could be a useful & generic spec across platforms, WDYT?

We may want to give it another name though, ComponentInstance could be confused with Component.

resouer avatar Sep 01 '19 05:09 resouer

We have cloud resources which are non-k8s. Two different App instances could depend on one Component instance in a shared mode.

hongchaodeng avatar Sep 02 '19 18:09 hongchaodeng