-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Group name configurable within ResourceGroup #164
Comments
I'm happy to pick this up! |
Here's how I was thinking this could be implemented:
Things I'm not sure about:
@a-hilaly can you please verify if I'm in the right direction before I start working on this? Thanks! |
@RinkiyaKeDad Thank you for picking this one up! The steps you described are correct and exactly what we need to do for this feature :) I'm not sure if we need to add any special labels for now. We can always do that in the future. |
Thinking out loud maybe we could keep using "apiVersion" to stay consistent with Kubernetes since most users are familiar with that convention? |
Feature Description
Problem Statement:
The
Group
name of the CRD created by aResourceGroup
is currently hardcoded. It would be beneficial to be able to define the group name to assist in differentiating kro specific CRDs and user/customer defined CRDs.Proposed Solution:
Add a
group
attribute withinspec.schema
which should default tokro.run
, similar to this:Alternatives Considered:
Additional Context:
The text was updated successfully, but these errors were encountered: