gansheer commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1927521472
The jib strategy are tested in e2e test - the builder workflow. The e2e
tests are thoses executed with a kubernetes environment. Also the default
strategy is used in lots of the
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1927361008
@gansheer I've made the [PR](https://github.com/apache/camel-k/pull/5137).
Also I noticed there aren't any tests for the publish strategies. Would you
happen to know if this
gansheer commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1926761811
@hernanDatgDev To make a backport you just need to do a PR on the
release-2.1.x branch.
--
This is an automated message from the Apache Git Service.
To respond to the message,
squakez commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1926432725
We can backport to 2.1.x and if it's an issue that is blocking any
production behavior we can make a patch release accordingly.
--
This is an automated message from the Apache Git
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1924811235
@gansheer I tried applying your fix to 2.1.0 and the Jib strategy is working
as expected. I believe that the logging in 2.1.0 w/ Jib simply was not detailed
enough so the
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1924400415
@gansheer What would it look like to take the 2.2.0 fix RE this issue and
patch it for v2.1.x? Could it really be as simple as taking the authentication
refactoring you did
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1885807384
Hey @gansheer, unfortunately neither of these options worked for me and I
tried other possibilities as well, but no luck. After all attempts I tried with
the latest
gansheer commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1884881524
@hernanDatgDev To make it work with Jib you should access to the docker hub
registry via `registry-1.docker.io`: `kamel install --registry
registry-1.docker.io`. That means using
gansheer commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1882578089
@hernanDatgDev Thanks for giving the detail of your installation.
I identified what you report while working on this issue #5017. There are
definitely some multiple custom
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1881804664
@gansheer Unfortunately I'm still facing this unauthorized 401 registry
issue with the latest release 2.2.0
This occurs in both my docker-desktop cluster and a local
squakez closed issue #5007: Integrations fail with Jib publish strategy
URL: https://github.com/apache/camel-k/issues/5007
--
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.
To
gansheer commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1874074880
@hernanDatgDev it is probably an issue with how the registry secret is
managed by the Jib publish strategy.
@squakez can you assign this to me ? I will look more into it.
--
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1868061433
Tried with camel-k v2.2.0 snapshot and received more information. Seems like
a problem accessing the docker registry. The same registry secret works with
Spectrum as the
hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1867877343
Install command camel-k v2.1.0:
`kamel install --registry docker.io --organization hguardado
--registry-secret dockerhub-cred --maven-settings
gansheer commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1867516492
Hi @hernanDatgDev, I can't reproduce your issue, it works well for me.
Can you give us more details on your use case: how you installed the
operator, with which configuration,
squakez commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1867423465
@gansheer can you please have a look?
--
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
hernanDatgDev opened a new issue, #5007:
URL: https://github.com/apache/camel-k/issues/5007
### What happened?
Integrations do not run with publish strategy Jib.
While using v2.1.0 the build fails before an image can be created with
minimal logging detail
While using v2.0.0 the
17 matches
Mail list logo
