From 93d46d982909efacc40fb00b4fca9dc3062fe0a9 Mon Sep 17 00:00:00 2001 From: Mukul Kumar Date: Thu, 26 May 2022 06:59:06 +0530 Subject: [PATCH] Update document regarding overrides Update configuration.md in clusterctl --- docs/book/src/clusterctl/configuration.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/book/src/clusterctl/configuration.md b/docs/book/src/clusterctl/configuration.md index 686a659ee10e..d81957187b96 100644 --- a/docs/book/src/clusterctl/configuration.md +++ b/docs/book/src/clusterctl/configuration.md @@ -89,6 +89,14 @@ Please note that the configuration above will be considered also when doing `clu ## Overrides Layer + + `clusterctl` uses an overrides layer to read in injected provider components, cluster templates and metadata. By default, it reads the files from `$HOME/.cluster-api/overrides`. @@ -168,7 +176,7 @@ overridesFolder: /Users/foobar/workspace/dev-releases Image override is an advanced feature and wrong configuration can easily lead to non-functional clusters. It's strongly recommended to test configurations on dev/test environments before using this functionality in production. -This feature must always be used in conjunction with +This feature must always be used in conjunction with [version tag](commands/init.md#provider-version) when executing clusterctl commands.