meshery
Model Generation: Support mapping of `group` field in CRDs
Current Behavior
The group field is a standard property in Kubernetes CustomResourceDefinitions (CRDs), not a custom property.
In Kubernetes CRDs, the group field specifies the API group for the custom resource being defined. API groups are used to organize Kubernetes resources and form part of the REST API path.
Desired Behavior
Enhance logic to include the ability to map components to models using the value found in the group field.
Implementation
Acceptance Tests
Notes
For example, monitor.azure.com is the API group for a custom resource. This means the resource belongs to the monitor.azure.com API group, which is defined by Azure Service Operator.
Contributor Guides and Handbook
- 🛠 Meshery Build & Release Strategy
- 📚 Instructions for contributing to documentation
- 🎨 Wireframes and designs for Meshery UI in Figma
- 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack
Thanks much for jumping in and volunteering. In an effort to help guarantee your success in undertaking assignment of the issue, will you:
- Confirm that you're able to build the project, specifically, the components necessary to resolve this issue.
- Confirm the approach you intend to take to resolve the issue.
@leecalcote I can confirm that i will be able to build this project as My local setup is ready , I can build and work on this issue without any technical blockers. My approach will be - For this issue, that would look like: 1.Identify where Meshkit currently maps components to models. 2.Extend the logic so that, in addition to existing identifiers which also checks the group field in the Kubernetes CRD. 3.Update the relevant functions to read and use the group value for mapping. 4.Add or update unit tests to verify this new mapping works
@leecalcote Please check the PR and let me know if anything more needs to be done...