gansheer closed issue #4841: unambigious reference to configmaps and secrets
URL: https://github.com/apache/camel-k/issues/4841
--
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.
gansheer commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-2061150710
Fixed by camel-k-runtime 3.8.1
--
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
aklemp opened a new issue, #4841:
URL: https://github.com/apache/camel-k/issues/4841
### Requirement
As a route developer I want to reference properties in existing configmaps
and secrets without collision to easier integrate to existing infrastructure
and to avoid managing globally
gansheer commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1966169811
@squakez @oscerd This needs to be reopen, I don't know why it was closed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
github-actions[bot] closed issue #4841: unambigious reference to configmaps and
secrets
URL: https://github.com/apache/camel-k/issues/4841
--
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
github-actions[bot] commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1928548803
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
squakez commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-179879
The above was fixed in the framework. We can keep it open and verify as soon
as we release next camel k runtime.
--
This is an automated message from the Apache Git Service.
To
aklemp commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1782469437
Sure, created https://issues.apache.org/jira/browse/CAMEL-20054
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
lburgazzoli commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1782409972
@aklemp can you please report an issue on Apache Camel here ?
https://issues.apache.org/jira/projects/CAMEL
--
This is an automated message from the Apache Git Service.
To
aklemp commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1782402507
For future reference, it is also working in YAML based integrations:
```yaml
spec:
traits:
mount:
configs:
- secret:some
jvm:
lburgazzoli commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1782389470
So I guess the issue is that `camel.k.mount-path.secrets` is uses for both
properties and env vars, whereas the env var should have been uppercase to
match what camel-k injects
aklemp commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1782387317
Stupid me. It works if being used correctly (i.e. `jvm.options` instead of
`jvm.config`). The value is referenced successful now.
--
This is an automated message from the Apache
aklemp commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1782377876
Did another check and it doesn't matter if I specify the `jvm.config` trait.
The resulting pod looks exactly the same and there is no evidence of any
impact. Especially the container
aklemp commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1781234083
Tried the following (not sure if my trait value is correct).
```
kamel run --trait
jvm.config="-Dcamel.k.mount-path.secrets=/etc/camel/conf.d/_secrets"
--config=secret:some
lburgazzoli commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1781193781
According to the
aklemp commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1781166493
I'm not into the details who is doing its magic (Camel, Camel K,
Kubernetes). However, I don't see the need to access REST API every time we use
the secret because they are mounted
squakez commented on issue #4841:
URL: https://github.com/apache/camel-k/issues/4841#issuecomment-1774622712
Camel K property setting via `kamel run -p` option is an helper provided in
the CLI. If the user has multiple keys with the same value, then, it's
something up to the user to know
aklemp opened a new issue, #4841:
URL: https://github.com/apache/camel-k/issues/4841
### Requirement
As a route developer I want to reference properties in existing configmaps
and secrets without collision to easier integrate to existing infrastructure
and to avoid managing globally
18 matches
Mail list logo
