Closed a-thaler closed 3 days ago
Decision got accepted
We identified that the "kyma" category will collide with the CRD called "kyma" and will confuse end users. As the use case of listing all kyma resources is maybe not really existent, we decided to remove the category from the proposal, I adjusted the description.
Created on 2024-06-04} by Andreas Thaler(@a-thaler)
Decision log
Context
It is hard to get an overview across the modules and the kyma status as all entities are modeled in individual CRDs, so you need to know what to query for.
It should be possible to list and get relevant Kyma resources with simple commands using kubectl. A typical approach is to leverage CRD categories. Having that simple 'kubectl get' will return all resources belonging to the category.
Considerations
There seem to be no official recommendation on when to use categories and how to name them. Istio is using:
gardener and calico seem to not use categories
Decision
All user facing CRDs should have categories attached in a consistent approach using the following pattern:
General categories:
Example CRD assignment categories: