---------------------- I'm sorry, but the provided knowledge sources do not contain information on how to increase the number of replicas for a Kaniko build in Garden. It's important to note that Kaniko operates by creating a separate pod for each build, rather than using a set number of replicas. For more detailed information, you may want to refer to the official Garden documentation or the Kaniko project on GitHub: - Garden Documentation () - Kaniko Project on GitHub () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- Based on the provided knowledge sources, there is no specific mention of a limit on the number of Kaniko pods that Garden can create. In fact, Garden's Kaniko build mode operates by creating an individual Kaniko pod for each image build, which allows it to scale horizontally and elastically. However, the actual number of Kaniko pods that can be created may be influenced by factors such as the resources available in your Kubernetes cluster and any specific configurations or restrictions in place. For more detailed information, you may want to refer to the official Garden documentation or the Kaniko project on GitHub: - Garden Documentation () - Kaniko Project on GitHub () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- Based on the information provided in the knowledge sources, the

cleanup

command in Garden does not directly support the

--var

flag. However, a workaround was suggested in a Github issue () where an environment variable can be used to set a timeout for the

cleanup

command. Here's the example provided:

bash
GARDEN_K8S_DELETE_NS_TIMEOUT_MS=900 garden cleanup namespace

In this case,

GARDEN_K8S_DELETE_NS_TIMEOUT_MS

is an environment variable used to set the timeout for the

cleanup

command. This approach could potentially be used to pass other variables to the

cleanup

command as well. For more information on how to use commands in Garden, you can refer to the official documentation (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- Yes, you're correct. The

--var

flag is indeed a global option in Garden, which means it can be used with any of the CLI commands. This flag allows you to set a specific variable value, using the format

<key>=<value>

. This will override any value set in your project configuration. You can specify multiple variables by separating them with a comma. Here's an example of how to use it:

bash
garden deploy --var some-key=custom-value

In this case,

some-key

is the variable name and

custom-value

is the value you're assigning to it. This command will deploy your project with the specified variable value. However, please note that the effect of the

--var

flag depends on how the command you're using interacts with the variables you're setting. If the

cleanup

command doesn't use the variable you're setting with the

--var

flag, then it won't have any effect. For more information, you can refer to the official documentation (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted