From bb612fae59be11b32ccbb1159e6bb944bd80c863 Mon Sep 17 00:00:00 2001 From: gitea_admin Date: Thu, 2 Apr 2026 13:16:34 +0000 Subject: [PATCH] Update Untime secret configuration --- Untime-secret-configuration.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/Untime-secret-configuration.md b/Untime-secret-configuration.md index de8917c..b73d584 100644 --- a/Untime-secret-configuration.md +++ b/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: \ No newline at end of file +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: \ No newline at end of file