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

How to specify the BaseImage when creating an integration? #2844

Closed
S96EA opened this issue Dec 30, 2021 · 4 comments · Fixed by #4816
Closed

How to specify the BaseImage when creating an integration? #2844

S96EA opened this issue Dec 30, 2021 · 4 comments · Fixed by #4816

Comments

@S96EA
Copy link

S96EA commented Dec 30, 2021

I want to use a different BaseImage(for example, a private image) instead of the default BaseImage.
I found that we can specify the platform when creating an integration (link), And the platform is bound to a BaseImage (link), but the BaseImage is not used because IncrementalImageContext,this step will find the integrationKit that already exists, these integrationKits do not use the new BaseImage.
So is there any other way we can change the default BaseImage?

@squakez
Copy link
Contributor

squakez commented Jan 3, 2022

If the IntegrationKit was created before updating the baseImage for the platform, then, yes, the algorithm will choose the best matching kit in between the existing ones, whichever was the baseImage from which it derived from. If you need to update all the Integration and the related kits, the best thing you can do is to kamel reset which will clean all the namespace. Of course, this is a disruptive action that will wipe all your running stuff.

@S96EA
Copy link
Author

S96EA commented Jan 4, 2022

How about adding a label to the integrationKit, which is used in the IncrementalImageContext step to filter IntegrationKits that use a certain baseImage?

@squakez
Copy link
Contributor

squakez commented Jan 4, 2022

Could be an idea in the context of the work requested for #2736

@github-actions
Copy link
Contributor

github-actions bot commented Apr 5, 2022

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@squakez squakez linked a pull request Oct 11, 2023 that will close this issue
squakez added a commit to squakez/camel-k that referenced this issue Oct 19, 2023
* Useful to know from which image a kit hierarchy started
* added builder.base-image property trait to override easily the base image

Ref apache#2844
squakez added a commit to squakez/camel-k that referenced this issue Oct 19, 2023
* Useful to know from which image a kit hierarchy started
* added builder.base-image property trait to override easily the base image

Ref apache#2844
squakez added a commit to squakez/camel-k that referenced this issue Oct 19, 2023
* Useful to know from which image a kit hierarchy started
* added builder.base-image property trait to override easily the base image

Ref apache#2844
squakez added a commit to squakez/camel-k that referenced this issue Oct 19, 2023
* Useful to know from which image a kit hierarchy started
* added builder.base-image property trait to override easily the base image

Ref apache#2844
squakez added a commit that referenced this issue Oct 20, 2023
* Useful to know from which image a kit hierarchy started
* added builder.base-image property trait to override easily the base image

Ref #2844
realMartinez pushed a commit to realMartinez/camel-k that referenced this issue Nov 13, 2023
* Useful to know from which image a kit hierarchy started
* added builder.base-image property trait to override easily the base image

Ref apache#2844
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants