From 829ebab9b5a0762e8020c7e5e83307f4e14ff847 Mon Sep 17 00:00:00 2001 From: gitea_admin Date: Thu, 2 Apr 2026 13:15:19 +0000 Subject: [PATCH] Update Untime secret configuration --- Untime-secret-configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Untime-secret-configuration.md b/Untime-secret-configuration.md index 5fb6528..65b7701 100644 --- a/Untime-secret-configuration.md +++ b/Untime-secret-configuration.md @@ -25,14 +25,14 @@ config-configmap-route.yaml ``` -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 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 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 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. +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: