squakez closed issue #5069: Bad revision when running jvm and native builds
with knative
URL: https://github.com/apache/camel-k/issues/5069
--
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
squakez commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-2042250987
Closing as waiting for feedback. Please, reopen if still facing any issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
squakez commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-2039590350
Waiting for some feedback before closing this.
--
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
squakez commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-2020701919
We have worked to several enhancement in version 2.3, I think this may have
been fixed during these developments. Would you mind testing this scenario
again with latest nightly to
lsergio commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-1900711844
During more experimentation, I ended up with a scenario that might have the
same root cause:
I created an Integration and provided less resources than it needs in the
lsergio commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-1893766512
I could not reproduce the error working directly with Knative. These are the
steps what I followed:
- Exported the yaml files for the config maps created by camel k:
squakez commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-1893654413
Thanks for the details. Then, it seems that the operator behavior is correct
as it applies the changes to the KSVC custom resource as it is expected. The
only additional thing it is
lsergio commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-1893603349
I inspected the ksvervices and this is what I found out:
- While only the jvm build is ready, the ksvc uses the jvm image and the
container command is echo exec java -Xmx210M
squakez commented on issue #5069:
URL: https://github.com/apache/camel-k/issues/5069#issuecomment-1893275300
Thanks for reporting. I have the vague feeling this is kind of unsupported
scenario. When we create the native build, what we do is creating a "native"
Deployment which attempts to
lsergio opened a new issue, #5069:
URL: https://github.com/apache/camel-k/issues/5069
### What happened?
I'm not sure if this is a Camel K or Knative issue. This is what happens:
I created an Integration with the following source code:
```
apiVersion: camel.apache.org/v1
10 matches
Mail list logo
