You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally, I think the SDK should focus on core functionality (and there's still a bit to do there) and leverage other tools fore additional support. Supporting RBAC/OLM generation at the SDK level would be quite an undertaking because none of the infrastructure needed for it exists.
If dependent resources used, it can be generated from that
We could introduce registering informers with annotations (this would make also managed dependent resources nicer, when sharing event source). And generate basic rback from that.
I really like Quarkus, but I think it's not ideal that some very useful features require using Quarkus. In an ideal world (and I know that this completely neglects the required effort for this), rbac-generation would be available as an additional dependency, like the crd-generator. This way, it would not be part of the core-SDK, but as a 'plugin'.
Activity
metacosm commentedon Feb 10, 2023
Personally, I think the SDK should focus on core functionality (and there's still a bit to do there) and leverage other tools fore additional support. Supporting RBAC/OLM generation at the SDK level would be quite an undertaking because none of the infrastructure needed for it exists.
csviri commentedon Feb 22, 2023
what do you mean by this exactly?
I see couple of options:
LucaMertens commentedon Apr 18, 2023
I really like Quarkus, but I think it's not ideal that some very useful features require using Quarkus. In an ideal world (and I know that this completely neglects the required effort for this), rbac-generation would be available as an additional dependency, like the crd-generator. This way, it would not be part of the core-SDK, but as a 'plugin'.
metacosm commentedon Apr 18, 2023
It's also worth noting that some of that functionality could be addressed at the operator-sdk plugin level.
[-]Moving OLM and RBAC related resource generator to the core [/-][+]Generate Kubernetes Resource a.k.a. RBAC [/+][-]Generate Kubernetes Resource a.k.a. RBAC [/-][+]Generate RBAC [/+]csviri commentedon Apr 27, 2026
Maybe we could re-visit this, since we have the helm chart, it is not the same thing of course, but not sure this worth the effort.
Just some wild though: we could add a flag to the helm chart, that on
helm templateit would just generate RBAC, but that would be a bit unorthodox.