---------------------- When using the

kubernetes

Deploy action in Garden, you can reference external manifest files in your project structure. This is done via the

spec.files

directive in your Garden configuration. Here's an example of how you can do this:

yaml
kind: Deploy
type: kubernetes
name: api
spec:
 files:
 - ./manifests/Deployment.yaml
 - ./manifests/Ingress.yaml
 - ./manifests/Service.yaml

You can also use glob patterns to reference all files in a directory:

yaml
kind: Deploy
type: kubernetes
name: api
spec:
 files:
 - ./manifests/*

If your manifests are in a parent directory relative to the action config file, you need to set the

source.path

field for your action since Garden cannot include files from parent directories. Here's an example:

yaml
kind: Deploy
type: kubernetes
name: api
source:
 path: ../ # <--- Garden will now treat the parent directory as the action source path
spec:
 files:
 - ./manifests/Deployment.yaml # <--- Reference the manifests relative to the source path
 - ./manifests/Ingress.yaml

For more information, you can refer to the Garden documentation (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- Hmm, I don't know enough to give you a confident answer yet. The provided knowledge sources do not contain information about referencing a Kubernetes manifest file hosted on GitHub. They only cover referencing local manifest files in the project structure. For more detailed information, you might want to check the official Garden documentation () or their GitHub repository (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted