---------------------- To address your question about using

garden tools kubectl

with the local-kubernetes provider and the correct context, I'll provide guidance based on the available information: a) To use the local-kubernetes provider over the ephemeral-kubernetes provider: You need to configure your project to use the local-kubernetes provider. This can be done in your project-level

garden.yml

file. Here's an example configuration:

yaml
apiVersion: garden.io/v1
kind: Project
environments:
  - name: local
providers:
  - name: local-kubernetes
    environments: [local]

This configuration sets up the local-kubernetes provider for the "local" environment. Make sure you're using the correct environment when running Garden commands. b) To use the correct context: The local-kubernetes provider attempts to automatically detect and set the appropriate context for connecting to your local Kubernetes instance. However, you can explicitly specify the context if needed. Here's how you can do that:

yaml
apiVersion: garden.io/v1
kind: Project
environments:
  - name: local
providers:
  - name: local-kubernetes
    environments: [local]
    context: minikube  # Replace with your desired context

Replace "minikube" with the specific context you want to use. By setting up your project configuration this way, when you run

garden tools kubectl

, it should use the local-kubernetes provider with the specified context. It's worth noting that if you have multiple Kubernetes environments (like Minikube and Docker for Mac with Kubernetes), Garden will choose the one configured as the current context in your

kubectl

configuration. If no current context is set, it will use the first available context.

For more detailed information, you can refer to the [Local-k8s Configure Provider]() documentation. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- To automatically use the configured context in run and test actions, you don't need to do anything extra. Once you've set up your project configuration with the local-kubernetes provider and specified the context (if necessary), Garden will automatically use that context for all operations, including run and test actions. Here's a brief explanation of how it works: 1. The context you've specified in your project configuration (or the automatically detected one if you didn't specify it) is used by the local-kubernetes provider for all Kubernetes-related operations. 2. When you run a command like

garden run

or

garden test

, Garden uses the provider configuration to determine which Kubernetes context to use. 3. This context is then automatically applied to all actions, including run and test actions, that interact with the Kubernetes cluster. For example, if your project configuration looks like this:

yaml
apiVersion: garden.io/v1
kind: Project
environments:
  - name: local
providers:
  - name: local-kubernetes
    environments: [local]
    context: my-local-context

When you run commands like

garden run ...

or

garden test ...

, they will automatically use the "my-local-context" for executing these actions. It's important to note that you don't need to specify the context in individual run or test action configurations. The context is managed at the provider level and applied globally to all actions that require Kubernetes access. For more information on how providers work in Garden, you can refer to the [Projects > How it Works > Providers]() documentation. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted