docs: multi-cluster (#941)

* docs: multi-cluster Signed-off-by: Charles-Edouard Brétéché <[email protected]> * client binding Signed-off-by: Charles-Edouard Brétéché <[email protected]> * kubeconfig Signed-off-by: Charles-Edouard Brétéché <[email protected]> --------- Signed-off-by: Charles-Edouard Brétéché <[email protected]>
kyverno · Feb 21, 2024 · f256b7d · f256b7d
1 parent 6838a61
commit f256b7d
Showing 1 changed file with 32 additions and 0 deletions.
diff --git a/website/docs/configuration/multi-cluster.md b/website/docs/configuration/multi-cluster.md
@@ -140,3 +140,35 @@ In the example below, `$client` binding is a client to the configured `cluster-1
                     (length(@)): 1
         # ...
     ```
+
+### KUBECONFIG in scripts and commands
+
+When a cluster is specified (whatever the `test`, `step` or `operation` level), a temporary `KUBECONFIG` is automatically created and the `KUBECONFIG` is set to this temporary file for every `command` and `script` operation.
+
+This way `command` and `script` operations are executed in the context of the configured cluster.
+
+!!! warning "Temporary KUBECONFIG"
+    The default `KUBECONFIG` you usually observe in your local shell will be different in `script` and `command` operations.
+
+!!! example "Temporary KUBECONFIG"
+
+    ```yaml
+    apiVersion: chainsaw.kyverno.io/v1alpha1
+    kind: Test
+    metadata:
+      name: example
+    spec:
+      steps:
+      - try:
+        # ...
+        - script:
+            # operation will be executed against the
+            # cluster specified below
+            cluster: cluster-1
+            # the kubectl command below will use a 
+            # KUBECONFIG environment variable pointing
+            # to a temporary kubeconfig file configured
+            # for the specified cluster
+            content: kubectl get pods
+        # ...
+    ```