-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add build item for extensions to contribute ClusterRoleBindings #43378
Conversation
This would also be a candidate for backport if possible. |
This comment has been minimized.
This comment has been minimized.
Is there an overall goal behind the backport requests? Because from what I can see, this one (and some of the others) qualify more as new features than as fixes. So except if we have a very pressing business requirements, I'm not so excited about backporting them. |
Understandable. However, quarkiverse/quarkus-operator-sdk#932 cannot be fixed without these particular features (or changes that would similarly expose information that isn't currently available to extensions). I wouldn't say that this is a pressing need, however it would be detrimental for this not to be in the next LTS, in my opinion. I realize it's pretty late in the cycle but we don't get to choose when issues appear or when we finally have time to work on them. This being available in some .x version of the next LTS would be fine with me, it doesn't need to be in the very first one as long as it's eventually there and doesn't have to wait for LTS + 1. |
534e5e2
to
679cb3d
Compare
Signed-off-by: Chris Laprun <claprun@redhat.com>
Status for workflow
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Chris Laprun claprun@redhat.com