-
Notifications
You must be signed in to change notification settings - Fork 350
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
Operator is not able to push builder image to the internal registry (OpenShift cluster) #4297
Comments
Thanks for reporting. Yes, we need to support S2I or any other Openshift way of building images, see https://github.com/apache/camel-k/blob/main/pkg/controller/catalog/initialize.go#L192 |
@squakez I would like to take care of adding the s2i (or any other openshift way) for the builder images generation. |
* Add initialize builder image on catalog with imagestream and buildconfig resource who's owner is the CamelCatalog * Light refactoring of S2I code Ref apache#4297
* Add initialize builder image on catalog with imagestream and buildconfig resource who's owner is the CamelCatalog * Light refactoring of S2I code Ref apache#4297
* Add initialize builder image on catalog with imagestream and buildconfig resource who's owner is the CamelCatalog * Light refactoring of S2I code Ref apache#4297
* Add initialize builder image on catalog with imagestream and buildconfig resource who's owner is the CamelCatalog * Light refactoring of S2I code Ref #4297
I think we can close this issue @squakez . The others follow up issues created does not prevent the feature from working. |
I have OpenShift cluster and I am testing Camel-K 2.0 nightly build. I would like to use OCP internal registry. I install Camel-K operator with the followngn command
kamel install --olm=false --maven-repository=https://repository.apache.org/content/repositories/snapshots@id=apache-snapshots@snapshots --operator-image docker.io/testcamelk/camel-k:2.0.0-nightly
Created IntegrationPlatform is
but the operator is not able to push the builder image
I did a little digging and it seems that the Catalog initialize action is trying to get the registry from the IntegrationPlatform which is empty in my case. See https://github.com/apache/camel-k/blob/main/pkg/controller/catalog/initialize.go#L80-L85. It seems that the image name is resolved as
/camel-k-runtime-quarkus-builder
that is substituted asdocker.io/camel-k-runtime-quarkus-builder
The text was updated successfully, but these errors were encountered: