-
Notifications
You must be signed in to change notification settings - Fork 345
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
Deprecate build kit at platform set-up time #1604
Labels
kind/question
Further information is requested
Comments
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 17, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 17, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 18, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 18, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 18, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 18, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 18, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Sep 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upon start-up, the integration platform set-up, the operator may automatically install some integration kits but it looks like this feature is not really useful and there's a risk that those pre-defined kits may get out of date as they are not based on the camel catalog.
Should we deprecated this functionality in camel-k 1.1.0 and then remove it in 1.2.0 ?
The text was updated successfully, but these errors were encountered: