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:16:34 +00:00
parent 2b18f37270
commit bb612fae59
1 changed files with 1 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Untime-secret-configuration.md

@ -24,19 +24,7 @@ config-configmap-route.yaml
- to: "log:info"
```
You can see that were 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))`
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 wont start until the resource will be made available.
Runtime secret configuration
We can apply the very same concept seen in the previous section for the Kubernetes Secret s.
As an example, let’s create a Secret named my-sec containing certain information. You can alternatively use any Secret you’ve already stored in your cluster:
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:
```
config-secret-route.yaml
@ -50,4 +38,4 @@ config-secret-route.yaml
- 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: