gitPratikSingh commented on PR #6926: URL: https://github.com/apache/camel-k/pull/6926#issuecomment-6639595646
Thanks for the quick follow-up. You're right that a fixed version can't be justified from the rules alone. One extraction route I can see: the deletable set is computed from the role rules today, but the version could come from the operator's own scheme instead of a hand-written table. `apis.AddToScheme` registers every type the operator manages — including the Knative and KEDA duck types — under its real group, version, and kind. So for each role rule with the delete verb, the GVK could be resolved by looking up the scheme's registered types for that group and resource (guessing the resource name from the kind the usual way), rather than pinning versions in the GC code. The list stays fully static, no API query, and versions track the types the operator is actually built with. Would that direction work for you, or do you see a problem with leaning on the scheme for this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
