Update Untime secret configuration

gitea_admin 2026-04-02 13:15:19 +00:00
parent fc239cf34a
commit 829ebab9b5

@ -25,14 +25,14 @@ config-configmap-route.yaml
``` ```
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: 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))` 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 wont start until the resource will be made available. 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 Runtime secret configuration
We can apply the very same concept seen in the previous section for the Kubernetes Secret 's. We can apply the very same concept seen in the previous section for the Kubernetes Secret s.
As an example, lets create a Secret named my-sec containing certain information. You can alternatively use any Secret youve already stored in your cluster: As an example, lets create a Secret named my-sec containing certain information. You can alternatively use any Secret youve already stored in your cluster: