christophd closed issue #5402: Cannot load Knative configuration from file or
env variable
URL: https://github.com/apache/camel-k/issues/5402
--
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 spec
christophd commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2074977740
I am having a look why Camel K requires Knative serving to use K_SINK
SinkBinding
--
This is an automated message from the Apache Git Service.
To respond to the message, please
matzew commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2074839298
OK. After I sorted the RBAC in #5410 and I was able to work around on this,
by simply applying the Serving CRD.
This should not be needed, but it gets me beyond the point.
`
lburgazzoli commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2074177228
From an historical POV, the initial integration with Knative was based on
the addressable resolver (hand written), then we switched to to K_SINK as it
was much simpler
--
This
christophd commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2072960603
okay, many thanks for the clarification. Addressable resolver makes sense
and I recall that we have that in place somewhere else in Camel K, too.
For the K_SINK injection -
matzew commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2072797028
We have a resolver for addressables:
https://github.com/knative/pkg/blob/main/resolver/addressable_resolver.go
And the addressable is basically a named type w/ a `apis.URL
matzew commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2072482517
There was no serving installed. I just added the "serivce" CRD, but not more.
A broker is an addressable type, see:
https://knative.dev/docs/concepts/duck-typing/#addressable
christophd commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2072439471
I guess one of the hacks was to also install Knative serving. I do not fully
understand how the Camel K operator should resolve the Knative broker URL if
there is no serving avail
matzew commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2071911223
I have no usage of Knative Serving, as that is a separate component. and I
dont want to use it :smile:
The pipe has the broker already, as reference:
```yaml
apiVersi
christophd commented on issue #5402:
URL: https://github.com/apache/camel-k/issues/5402#issuecomment-2071904465
Hello Matthias,
I think this error is happening when K_SINK envvar injection is not
happening for the Integration deployment. I recall that the K_SINK injection
requires Kn
matzew opened a new issue, #5402:
URL: https://github.com/apache/camel-k/issues/5402
### What happened?
Installing pure Knative Eventing (just upstream knative eventing) and
Camel-K 2.3 via helm, from scripts:
*
https://github.com/matzew/eventing-cloud-integraton/blob/main/sys
squakez closed issue #654: Cannot load Knative configuration from file or env
variable
URL: https://github.com/apache/camel-k/issues/654
--
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
squakez commented on issue #654:
URL: https://github.com/apache/camel-k/issues/654#issuecomment-2064238965
I think this is no longer relevant after the changes introduced in
https://github.com/apache/camel-k/pull/5186 - please, create a new issue if any
other problem happens again.
--
Th
13 matches
Mail list logo
