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

Use Camel 4.9.0 by default for Camel JBang #787

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

apupier
Copy link
Member

@apupier apupier commented Dec 4, 2024

No description provided.

@apupier
Copy link
Member Author

apupier commented Dec 19, 2024

@dependabot rebase

@apupier
Copy link
Member Author

apupier commented Dec 19, 2024

screenshot from the failing test with deployment
Camel standalone file deployment using Camel JBang Kubernetes Run Deploy integration to Kubernetes (Minikube)

EDIT: for this one, reproducing locally with Minikube manually. it seems that now the cluster type MUST be set to kubernetes to have it working, previously even with openshift set it was able to do the deploy anyway, so the test must be adapted and change the preference

By default, Camel Jbang is now using Jib and not Docker and providing a
multi-arch platform and the way to produce images are no more the same
consequently:
* a specific registry must be configured. We found only using Docker to
make it working with Minikube.
* qemu is required for the multi-arch with Docker
* resgitry-alias is required because vs code tasks cannot escape and
interpret correctly the env command of the registry setup

note that it is fixing the deploy only.

The debug (and so remaining test failures) is not working due to
https://issues.apache.org/jira/browse/CAMEL-21612

Signed-off-by: Aurélien Pupier <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant