You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/12/12 09:51:01 UTC
[GitHub] [camel-k] agiertli opened a new issue, #3891: Allow traits to be configured via configmap/secrets
agiertli opened a new issue, #3891:
URL: https://github.com/apache/camel-k/issues/3891
Right now the trait configuration values are hardcoded in the Integration or KLB itself.
It would be useful to have a possibility to externalize that configuration. Example CLI command could look like:
-t container.cpu={{comfigmap:mycm/cpu}}
This is especially important in context of "kamel promote" feature, because if you can't externalise config, then you are forced to re-use the same trait configuration values across environment. Good example is container trait - where you typically have different values for mem/cpu/replicas across dev and prod.
--
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 #3891: Allow traits to be configured via configmap/secrets
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #3891:
URL: https://github.com/apache/camel-k/issues/3891#issuecomment-1426026139
With the presence of the dry-run provided in #4050 it should makes sense to post process any profile with Kustomization style approach. Ideally with the new feature, you will `kamel promote ... -o yaml` that would produce an Integration CR on top of which we can apply any customization via `kubectl apply -k`. I am closing this in favour of the aforementioned approach.
--
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 #3891: Allow traits to be configured via configmap/secrets
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3891:
URL: https://github.com/apache/camel-k/issues/3891#issuecomment-1346190296
It could be that one, or maybe also any properties available in `application.properties`, being the properties also configurable from a Configmap or a Secret.
--
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 #3891: Allow traits to be configured via configmap/secrets
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #3891: Allow traits to be configured via configmap/secrets
URL: https://github.com/apache/camel-k/issues/3891
--
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