---------------------- Based on the information in the knowledge sources, Garden's

kubernetes

Deploy action allows you to specify Kubernetes manifests either by referencing local files (using the

spec.files

or

spec.manifestFiles

fields) or by including them inline in your configuration. The documentation consistently shows examples where manifest files are referenced from the local filesystem, not directly from a remote URL. For example, you would typically configure it like this:

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

or with glob patterns:

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

There is no mention in the documentation of supporting direct URLs to remote manifest files (such as a GitHub release asset) in the

files

or

manifestFiles

fields. The recommended approach is to download the manifest file to your project directory and then reference it locally in your Garden configuration [see example](). Summary: You cannot directly deploy Kubernetes manifest files from a URL with Garden's

kubernetes

Deploy action. You need to download the manifest file first and then reference it as a local file in your configuration. If you need to automate this, consider adding a script or a pre-step in your workflow to fetch the manifest before running Garden. [Reference: Deploying K8s Resources]() ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- The knowledge sources do not explicitly mention whether symlinking

.gitignore

to

.gardenignore

in a subdirectory is supported or recommended. However, Garden treats

.gardenignore

files using the same syntax and semantics as

.gitignore

files, and you can place

.gardenignore

files anywhere in your repository, including subdirectories, to control what is ignored in those locations [see here](). There is no documentation stating that symlinks are not supported, but also no confirmation that they are. If you want to use the same ignore patterns in a subdirectory, you could try symlinking

.gardenignore

to

.gitignore

in that subdirectory. If this does not work as expected, the recommended approach would be to copy the contents of

.gitignore

into a

.gardenignore

file in that subdirectory. In summary: There is no official documentation confirming support for symlinking

.gardenignore

to

.gitignore

in a subdirectory. You may try it, but if it does not work, use a separate

.gardenignore

file with the desired patterns in that subdirectory [see here](). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted