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 a "namespace" label to help group kamelets #640
Comments
Makes sense |
or maybe review how the group is used and i.e instead of |
Originally it was done in that way because if we had multiple kamelets for the same AWS service, they would have been filtered in the site view. But yeah, makes sense too |
or maybe we can use a convention like kamelet.group is always like namespace [+ kind] so in the case of namespace = AWS |
I think it should work in this way, I'm not sure if the annotations are currently used in camel-k too, need to have a look. |
As today we have a
kamelet.group
label that is used to group related kamelets together:It would be nice to add an additional label to define a larger group of related kamelets, like
kamelet.namespace
:The text was updated successfully, but these errors were encountered: