made group name configurable within resourcegroup

[RinkiyaKeDad]

Issue #, if available: #164

Description of changes:

• Adding Group string to the schema in kro/api/v1alpha1/resource_group.go
• Passing this information to the buildInstanceResource function in kro/internal/graph /builder.go
• Further passing this info to SynthesizeCRD in kro/internal/graph /builder.go to get the new CRD which would have the group info.
• Updating the extractCRDName function to accomodate the newly added Group field during deletion.
• Updating the GetResourceGroupInstanceGVK and GetResourceGroupInstanceGVR functions in kro/internal/metadata/groupversion.go

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[RinkiyaKeDad]

@a-hilaly I need some help figuring out how do I run kro locally to test my changes. I created an issue to document this process as well: #177

This is what I tried:

• Installed kro using the helm chart in a local k3d cluster.
• Ran make run after making my changes so that I could test them

I assumed this would have the controller running locally on my machine and the cluster would use that instead of the helm installed one but that was not the case because I kept getting this error:

❯ k apply -f resourcegroup.yaml
Error from server (BadRequest): error when creating "resourcegroup.yaml": ResourceGroup in version "v1alpha1" cannot be handled as a ResourceGroup: strict decoding error: unknown field "spec.schema.group"

Can you please help out with how do I run these changes I made to kro locally? I can then create a guide and add to the CONTRIBUTING.md as well for future contributors.

[michaelhtm]

Hey @RinkiyaKeDad, thanks for contributing to kro
Good catch, I will take a look at the Contributing doc.

After making changes, you can run the controller locally with the following command:

go run -tags=dev cmd/controller/main.go 

Make sure to install the updated CRD when making changes to it, if you haven't already.