You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/07/23 12:59:34 UTC
[GitHub] [camel-k] nicolaferraro opened a new issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
nicolaferraro opened a new issue #1636:
URL: https://github.com/apache/camel-k/issues/1636
We should upgrade the eventing resources to v1beta1 at least.
E.g. Subscription is no longer present at version v1alpha1.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669164931
> > > This will be fixed in next patch release.
> > > Until then, a simple workaround is this one. Instead of:
> > > ```
> > > from("knative:channel/xxx")
> > > ```
> > >
> > >
> > > Use:
> > > ```
> > > from("knative:endpoint/default")
> > > ```
> > >
> > >
> > > This will create a Knative service. Then you can create a subscription resource by hand to bind the channel to the service: https://knative.dev/docs/eventing/event-delivery/
> >
> >
> > But one question, I have in the producer this:
> > .to("knative:channel/creacionpac")
> > and in the consumer, I have this:
> > from("knative:channel/creacionpac")
> > I have to change both of them, or only the consumer?
> > Which is the workaround solution?
>
> Only the consumer
But where must I to indicate the name of the channel, creacionpac?
apiVersion: messaging.knative.dev/v1
kind: Subscription
metadata:
name: with-dead-letter-sink
spec:
channel:
apiVersion: messaging.knative.dev/v1
kind: InMemoryChannel
name: default
delivery:
deadLetterSink:
ref:
apiVersion: serving.knative.dev/v1
kind: Service
name: error-handler
subscriber:
uri: http://doesnotexist.default.svc.cluster.local
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669130187
> This will be fixed in next patch release.
>
> Until then, a simple workaround is this one. Instead of:
>
> ```
> from("knative:channel/xxx")
> ```
>
> Use:
>
> ```
> from("knative:endpoint/default")
> ```
>
> This will create a Knative service. Then you can create a subscription resource by hand to bind the channel to the service: https://knative.dev/docs/eventing/event-delivery/
But one question, I have in the producer this:
.to("knative:channel/creacionpac")
and in the consumer, I have this:
from("knative:channel/creacionpac")
I have to change both of them, or only the consumer?
Which is the workaround solution?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-697771092
Hi @MaciekLeks, we're adding auto-discovery for KafkaChannel v1beta1 in next 1.2.0 release.
Running with 1.1.1, if you want to use v1beta1 in the subscription you need to write an URL like:
```
from('knative:channel/salesforce?kind=KafkaChannel&apiVersion=v1beta1')
```
And it should do what you expect.
You won't need to specify kind & api in 1.2.0.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669839942
Other question, how can i invoke to an external url, because if i try to call to an external url in a knative integration, gives me one error, endpoint not found. I invoke the external url using recipientslist.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] MaciekLeks commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
MaciekLeks commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-697366452
@nicolaferraro Thanks for the update, but in case of Kafka channel it would not work correctly for v1beta1. `kamel run <integration>` creates subscription like this:
```yaml
channel:
apiVersion: messaging.knative.dev/v1alpha1
kind: KafkaChannel
name: salesforce
subscriber:
ref:
apiVersion: serving.knative.dev/v1
kind: Service
name: camel-k-kafa-consumer
```
So the channel must be declared for v1alpha1, like so:
```yaml
apiVersion: messaging.knative.dev/v1alpha1
kind: KafkaChannel
metadata:
name: salesforce
```
I've not checked out what about InMemoryChannel but I may assume it's the same.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro closed issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro closed issue #1636:
URL: https://github.com/apache/camel-k/issues/1636
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669122173
This will be fixed in next patch release.
Until then, a simple workaround is this one. Instead of:
```
from("knative:channel/xxx")
```
Use:
```
from("knative:endpoint/default")
```
This will create a Knative service. Then you can create a subscription resource by hand to bind the channel to the service: https://knative.dev/docs/eventing/event-delivery/
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669240559
> Like:
>
> ```yaml
> apiVersion: messaging.knative.dev/v1beta1
> kind: Subscription
> metadata:
> name: mysubscription
> spec:
> channel:
> apiVersion: messaging.knative.dev/v1
> kind: InMemoryChannel
> name: your-source-channel
> subscriber:
> ref:
> apiVersion: serving.knative.dev/v1
> kind: Service
> name: the-name-of-your-integration
> ```
Which is the relation with the from in the consumer?
from("knative:endpoint/default")
This default, what must be?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669842330
> Other question, how can i invoke to an external url, because if i try to call to an external url in a knative integration, gives me one error, endpoint not found. I invoke the external url using recipientslist.
It shouldn't matter what kind of integration you're running, to call an external URL you should use the `http` component, like `.to("http://theurl/thepath")`.
Btw, you can ask questions in the Gitter channel, to avoid polluting issues.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-670381212
> > Other question, how can i invoke to an external url, because if i try to call to an external url in a knative integration, gives me one error, endpoint not found. I invoke the external url using recipientslist.
>
> It shouldn't matter what kind of integration you're running, to call an external URL you should use the `http` component, like `.to("http://theurl/thepath")`.
>
> Btw, you can ask questions in the Gitter channel, to avoid polluting issues.
Sorry, I know that this issue is not related with the last two questions that I have asked you. But I have asked in the Gitter channel, and I don't have reply. The question is:
I have one question, I have some integrations in camel-k and knative, and I want to know how can I propagate the body from the first knative service to the last one? Because I need to have available in all the integrations.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669120167
Which is the solution to solve this issue? I have one channel consumer, and I have this error, I can't deploy the integration properly...
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669157355
> > This will be fixed in next patch release.
> > Until then, a simple workaround is this one. Instead of:
> > ```
> > from("knative:channel/xxx")
> > ```
> >
> >
> > Use:
> > ```
> > from("knative:endpoint/default")
> > ```
> >
> >
> > This will create a Knative service. Then you can create a subscription resource by hand to bind the channel to the service: https://knative.dev/docs/eventing/event-delivery/
>
> But one question, I have in the producer this:
>
> .to("knative:channel/creacionpac")
>
> and in the consumer, I have this:
>
> from("knative:channel/creacionpac")
>
> I have to change both of them, or only the consumer?
>
> Which is the workaround solution?
Only the consumer
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] pjcubero commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
pjcubero commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669776741
Ok, thanks a lot Nicola... I think I need to follow learning all of this technology... Thanks for your continuous support...
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669167127
Like:
```yaml
apiVersion: messaging.knative.dev/v1beta1
kind: Subscription
metadata:
name: mysubscription
spec:
channel:
apiVersion: messaging.knative.dev/v1
kind: InMemoryChannel
name: your-source-channel
subscriber:
ref:
apiVersion: serving.knative.dev/v1
kind: Service
name: the-name-of-your-integration
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro commented on issue #1636: No matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1"
Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1636:
URL: https://github.com/apache/camel-k/issues/1636#issuecomment-669769279
> > Like:
> > ```yaml
> > apiVersion: messaging.knative.dev/v1beta1
> > kind: Subscription
> > metadata:
> > name: mysubscription
> > spec:
> > channel:
> > apiVersion: messaging.knative.dev/v1
> > kind: InMemoryChannel
> > name: your-source-channel
> > subscriber:
> > ref:
> > apiVersion: serving.knative.dev/v1
> > kind: Service
> > name: the-name-of-your-integration
> > ```
>
> Which is the relation with the from in the consumer?
>
> from("knative:endpoint/default")
>
> This default, what must be?
Just "default", you don't have to change it. That uri exposes a knative endpoint, the name is irrelevant so we conventionally set it to "default".
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org