There are two proposed changes to the component CRD version:
Removal of the componentKinds fields (that came from the Kubernetes Application CRD that was one of the inspirations for the component CRD). The Kubernetes Application CRD supports the Google Kubernetes Marketplace, that is a more general-purpose (but standalone) app marketplace. With ODA components, the proposal is to be more prescriptive and only support certain Kubernetes resources). https://github.com/tmforum-oda/oda-component-ctk/issues/22
Standardization of the exposedAPI and dependentAPI structure across the coreFunction, Management and Security segments of the component definition. Creating the Canvas BDD has highlighted some inconsistencies in how the different segments were modeled. The proposal is in the issue: https://github.com/tmforum-oda/oda-component-ctk/issues/25
The issue is to change the component webhook microservice so that it automatically translates to/from the existing versions and the v1beta1 version.
Description
There are two proposed changes to the component CRD version:
Removal of the componentKinds fields (that came from the Kubernetes Application CRD that was one of the inspirations for the component CRD). The Kubernetes Application CRD supports the Google Kubernetes Marketplace, that is a more general-purpose (but standalone) app marketplace. With ODA components, the proposal is to be more prescriptive and only support certain Kubernetes resources). https://github.com/tmforum-oda/oda-component-ctk/issues/22
Standardization of the exposedAPI and dependentAPI structure across the coreFunction, Management and Security segments of the component definition. Creating the Canvas BDD has highlighted some inconsistencies in how the different segments were modeled. The proposal is in the issue: https://github.com/tmforum-oda/oda-component-ctk/issues/25
The issue is to change the component webhook microservice so that it automatically translates to/from the existing versions and the v1beta1 version.