Skip to content
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

Access channel in different namespace #3009

Closed
himanshumps opened this issue Feb 13, 2022 · 5 comments
Closed

Access channel in different namespace #3009

himanshumps opened this issue Feb 13, 2022 · 5 comments
Labels
area/knative Related to Knative kind/question Further information is requested status/stale

Comments

@himanshumps
Copy link

How do I access the channel in different namespace?

knative:channel/channel-name???

@himanshumps
Copy link
Author

Even the knative endpoint is not working if I give the service url

@astefanutti
Copy link
Member

Cross-namespace references to Knative channels has been added in Knative 0.22 and has yet to be supported in Camel K: #2201.

@astefanutti astefanutti added area/knative Related to Knative kind/question Further information is requested labels Feb 14, 2022
@himanshumps
Copy link
Author

But why the endpoint reference to different namespace channel(Inmemory chanel) with svc.cluster.local does not work. If it is a post over http, it should be supported

@himanshumps
Copy link
Author

I tried creating a kamelet binding with uri option from source channel in one workspace to destination channel in another workspace with uri option as well but that also did not work.

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/knative Related to Knative kind/question Further information is requested status/stale
Projects
None yet
Development

No branches or pull requests

2 participants