-
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
Delete knative warning when Knative is not installed #2397
Comments
I'm happy to take a look at this if no one else already is! |
@dimitraz great, feel free to go ahead. I think we can use that opportunity to revisit the |
Getting this error when trying to deploy a KameletBinding onto a minikube cluster with the Camel K Operator running in the same namespace. The creation of the integrations fails and periodically prints out this message.
Any possible fixes for this one? |
@astefanutti about your suggestion to revisit the |
@claudio4j about my suggestion, the current implementation, that lists particular Knative resources in the namespace, barely check the presence of the Knative CRDs in the cluster, so it's not really scoped to the namespace. It could well be replaced with checking the discovery API if the Knative APIs are present, using camel-k/pkg/util/kubernetes/discovery.go Line 25 in e955394
IsInstalled function, whose result would be equivalent.
For scoping the check to the namespace, I wonder if the Then, for the log message, I think it could be removed altogether, or moved to the knative trait, in the |
This issue has been automatically marked as stale due to 90 days of inactivity. |
I'd like to work on this |
How do I reproduce this bug |
@KuthumiPepple When you run the camel-k-operator in a namespace with no knative resources,it will print the mentioned output in the camel-k-operator pod log. |
@claudio4j So I built the operator with |
You should just install camel-k-operator in the kubernetes cluster and watch the camel-k-operator log. The |
@KuthumiPepple Since it's been inactive for long time, let me unassign it from you. |
That's OK.
…On Fri, 2 Dec 2022, 06:34 Tadayoshi Sato, ***@***.***> wrote:
@KuthumiPepple <https://github.com/KuthumiPepple> Since it's been
inactive for long time, let me unassign it from you.
—
Reply to this email directly, view it on GitHub
<#2397 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHKFLHJ7MENIQM74F7UWRYTWLGC6RANCNFSM46QWWGAA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
i am trying to create kamlet for kafka source as below
Getting below error logs in camel-k-operator. Is there any step am I missing here? Do I need to provide some other configuration besides?
|
@nchudasmasumo I think you better log a new issue, as it looks completely different from the one discussed in this one. |
This issue should be already fixed with 3652ee7 |
The operator prints periodically this info:
It looks like an error, while it's not. That log should be suppressed.
The text was updated successfully, but these errors were encountered: