camel.apache.org/aws-ddb-sink
1
0
Fork 0
generated from camel.apache.org/kamelet
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Untime secret configuration

gitea_admin 2026-04-02 13:14:47 +00:00
parent b20e7bbb7a
commit fc239cf34a
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Untime-secret-configuration.md

@ -12,7 +12,8 @@ As an example, let’s create a Configmap named my-cm containing certain informa
`kubectl create configmap my-cm --from-literal=my-configmap-key="configmap content"` `kubectl create configmap my-cm --from-literal=my-configmap-key="configmap content"`
We want to use the materialized file in an integration: We want to use the materialized file in an integration:
```config-configmap-route.yaml ```
config-configmap-route.yaml
- from: - from:
uri: "timer:configmap" uri: "timer:configmap"
steps: steps:
@ -20,10 +21,13 @@ We want to use the materialized file in an integration:
simple: "resource:classpath:my-configmap-key" simple: "resource:classpath:my-configmap-key"
- setBody: - setBody:
simple: "configmap content is: ${body}" simple: "configmap content is: ${body}"
- to: "log:info"``` - to: "log:info"
```
You can see that we’re expecting to use a my-configmap-key file stored somewhere in the classpath. In order to materialize the Configmap will be as easy as running the --config configmap syntax: You can see that we’re expecting to use a my-configmap-key file stored somewhere in the classpath. In order to materialize the Configmap will be as easy as running the --config configmap syntax:
kamel run --config configmap:my-cm config-configmap-route.yaml kamel run `![](![](--config configmap:my-cm config-configmap-route.yaml))`
As soon as the Integration starts, the Camel K operator will take care to mount a volume with the Configmap 's content. As soon as the Integration starts, the Camel K operator will take care to mount a volume with the Configmap 's content.
you can provide a Configmap which is not yet available on the cluster. The Integration won’t start until the resource will be made available. you can provide a Configmap which is not yet available on the cluster. The Integration won’t start until the resource will be made available.
@ -35,7 +39,8 @@ As an example, let’s create a Secret named my-sec containing certain informati
kubectl create secret generic my-sec --from-literal=my-secret-key="very top secret" kubectl create secret generic my-sec --from-literal=my-secret-key="very top secret"
We want to use the materialized secret file in an integration: We want to use the materialized secret file in an integration:
```config-secret-route.yaml ```
config-secret-route.yaml
- from: - from:
uri: "timer:secret" uri: "timer:secret"
steps: steps:
@ -43,5 +48,7 @@ We want to use the materialized secret file in an integration:
simple: "resource:classpath:my-secret-key" simple: "resource:classpath:my-secret-key"
- setBody: - setBody:
simple: "secret content is: ${body}" simple: "secret content is: ${body}"
- to: "log:info"``` - to: "log:info"
```
You can see that we’re expecting to use a my-secret-key file stored somewhere in the classpath. In order to materialize the Secret will be as easy as running the --config secret syntax: You can see that we’re expecting to use a my-secret-key file stored somewhere in the classpath. In order to materialize the Secret will be as easy as running the --config secret syntax: