You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "gansheer (via GitHub)" <gi...@apache.org> on 2023/07/04 08:02:48 UTC

[GitHub] [camel-k] gansheer opened a new issue, #4525: Builder image name missing the organization configuration

gansheer opened a new issue, #4525:
URL: https://github.com/apache/camel-k/issues/4525

   **Version:** Camel-k main branch (2.x)
   
   When installing Camel-k with a defined `organization` id/name with build strategy `pod` the builder image full name does not contains the `organization` id/name. I think it should (like with the kit image):
   
   ```
   REPOSITORY                                               TAG               IMAGE ID       CREATED          SIZE
   apache/camel-k                                           2.0.0-SNAPSHOT    abda4a06c8c4   15 minutes ago   637MB
   10.100.246.9/myorg/camel-k-kit-cihsu2p5tpl20drnif60   <none>            a18953b17581   2 weeks ago      516MB
   10.100.246.9/camel-k-runtime-quarkus-builder             2.16.0-snapshot   0a3d865dd0dc   2 months ago     1.08GB
   ```
   
   The command used to install is:
   ```
   kamel install --build-strategy pod --organization  myorg
   ```
   


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4525: Builder image name missing the organization configuration

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4525:
URL: https://github.com/apache/camel-k/issues/4525#issuecomment-1619876680

   Trying to use a private registry we're getting some auth problems:
   ```
         message: 'HEAD https://index.docker.io/v2/library/camel-k-runtime-quarkus-builder/manifests/2.16.0-snapshot:
           unexpected status code 401 Unauthorized (HEAD responses have no body, use
           GET for details)'
   ```


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4525: Builder image name missing the organization configuration

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4525:
URL: https://github.com/apache/camel-k/issues/4525#issuecomment-1619753360

   I don't think the org should apply to the dynamic image builder. IMO we need the builder to be as much generic as possible and reused if we have several IntegrationPlatforms (hence, several organizations).


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] gansheer commented on issue #4525: Builder image name missing the organization configuration

Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer commented on issue #4525:
URL: https://github.com/apache/camel-k/issues/4525#issuecomment-1619773024

   What will happen if we have non-compatible registry configurations (example with auth) in different IntegrationPlatforms ? Do we rebuild the builder image ?


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez commented on issue #4525: Builder image name missing the organization configuration

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4525:
URL: https://github.com/apache/camel-k/issues/4525#issuecomment-1619793265

   > What will happen if we have non-compatible registry configurations (example with auth) in different IntegrationPlatforms ? Do we generate a another builder image ?
   
   Good point. In general we need to revisit the entire concept of the dynamic builder, which is something that may be just temporary. If we evaluate for now it requires some enhancement like the one you're proposing, probably it makes sense to do it. Thanks.


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-k] squakez closed issue #4525: Builder image name missing the organization configuration

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #4525: Builder image name missing the organization configuration
URL: https://github.com/apache/camel-k/issues/4525


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org