tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1326795463
Current status: retracted the PR because the build is failing at a weird
point (unittests of the client, even before the Operator is being built...).
Will fiddle in my own fork an
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1319052745
Current status: ready for polishing. All pipeline errors are due to #3817 or
timeouts that are also already known. Next up: parameterize the build archs.
--
This is an automated
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1318832841
Integration tests are failing due to:
```
Error: p.go:274: >
{"level":"error","ts":1668698213.7254713,"logger":"camel-k.maven.build","msg":"\t[error]:
Build step io
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1318595629
So, the issue is:
- The `IMAGE_NAME` is set in the `secrets.E2E_CLUSTER_CONFIG` secret to
`kind-registry:5000/apache/camel-k` (I think, its a secret!)
- The `IMAGE_NAME`
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1318517323
Question for whoever is reading this: when pushing the image to the
kind-registry, the following error occurs:
```
#22 ERROR: failed to do request: Head
"https://kind-re
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1318387167
> * I know how buildx works
Foreshadowing quote was exactly that. I'm afraid i'll break the build
because with multi-arch images we can't rely on the local image store (see
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1317730696
So, based on the assumptions:
- ubi-quarkus-mandrel v22.0.0.2-Final-java11 is the version to target (v21
doesnt have arm builds)
- hosting the application in the new quarkus
tobiasoort commented on issue #1238:
URL: https://github.com/apache/camel-k/issues/1238#issuecomment-1315852692
> Can we close this issue?
Not really. The current state on Apple M1/M2 is that you can follow the
how-to, but 'kamel install' will install an amd64 image based pod (image
