-
Notifications
You must be signed in to change notification settings - Fork 352
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
A better name for KameletBinding #2625
Comments
@christophd since you're already making some work on Kamelets and we are discussing the opportunity to promote the Kamelets API to v1, I think it would be a good opportunity to have a look at this as well. |
I've just realized the the CRD type "Binding" may not be a good name. When we try to get the CR from Kube we got some error:
@lburgazzoli @astefanutti wdyt? IMO we are safe to use it, but it may create some problem in the future. Since we're still in time, maybe we can call it |
What about |
I think we should avoid the name clash with the reserved K8s resource |
Maybe Pipe ? |
I'm thinking on
|
Finally, |
When the KameletBinding concept was introduced in camel-k, if was meant to bind two Kamelets and nothing more, but over time we have added more capabilities, like:
So I think the term KameletBinding is not more appropriate and to reduce confusion, following the discussion on the dev mailing list, we should rename
KameletBinding
toBinding
The text was updated successfully, but these errors were encountered: