I'm trying to create HorizontalPodAutoscaler using $forEach to generate all the manifests and keep it DRY but I don't see a way to get an array of all the module names in the template string docs. It's not the first time this would be useful and usually I work around it but this time I don't see anything that wouldn't rely on just listing the modules by hand and then having to maintain that list up to date.

Hey all, how do I uninstall garden.io completely on MacOS? Simply running

brew remove garden-cli

still leaves garden running (tried going to http://localhost/something and got the garden 404 page still that says it's running)

Hello! I'm currently building a dev cluster of sorts where I want myself a few others to be able to deploy their code to run in isolated namespaces. I'm pretty much done with everything, but one problem I have is that some resources, like

ExternalDNS

, are not specific to a particular developer's namespace. What would be the recommended way to manage deployments that are done at the cluster level vs deployments done for a particular namespace. (I know my wording is confusing - i'm not really sure the best way to phrase the question 😛 )

Hi all, is there any guide how to optimize Kaniko in cluster build. We currently have the problem that we run into timeout with yarn builds for the react frontend because the CPU is exhausted. How can i scale Kanikopods independently via garden.

How to ask Garden to deploy a service in dev mode and its dependencies only vs. entire stack defined in garden.yml file? For example, my master garden file has configuration for all projects within our organization. I don't want all services to get deployed in K8. I want the service I'm working on being deployed in dev mode with its dependencies in regular deployed mode. Looking at the examples https://docs.garden.io/reference/commands#garden-deploy its not clear.

Hello, I am trying to use ModuleTemplate. While trying to deploy the service, I am unable to add

buildArgs

to the

templated

module. I get the error

key "buildArgs" is not allowed at path [buildArgs]

If I try to add

buildArgs

in the template itself and use

${inputs.XXX}

it complains

Could not find key inputs. Available keys: command, git, local, project and secrets.

Basically it looks like inside the template I can not use

inputs

except in the

modules

section. So currently as it stands I can not use

buildArgs

with

templates

. This is a blocker for using this feature. Is there any other way around it?

Wondering if it is possible to cache exec modules? For my stack I first run a build (not a task, so I can run tests on the build) to generate my executables that I copy into my containers. Currently using exec reruns this every time. I understand that for the other modules the caching behavior is baked in and there is no simple way to cache exec calls. Maybe I have to wait for the plugin SDK?

Can we define a new

ModuleTemplate

based off an existing one? The idea here is the project is giving, same template X and then a set of modules can create their own template Y based of template X and define the arguments that are common for all of it's services instead of repeating them for each template of the base template X. Can this be done? I tried an example but I can't get it to work

Hello, guys! So the problem is that i cant access my services within cluster with HTTP-requests. For example, i have two services:

frontend and api-gateway

. Their ports are respectively 3000 and 3001. The main issue is that i cant do a HTTP-request to http://api-gateway:3001 ( i get an

ERR_NAME_NOT_RESOLVED

). I can only do that using

external IP-address (http://127.10.0.7:3001)

. When i used Docker Compose, i had no problems with getting access to the other services with

api-gateway:3001

. I am sorry in advance for it, but can i ask one more question? I run my own test in Garden, but i cant see the

succeed

option in the Dashboard near it. It uses Jest-library to run the test. And it really passes it. Thanks in advance!

Hi, is there any planned work / update for garden to start supporting OCI helm repos? Currently it completely does not work, and bitnami is (slowly but surely) updating their charts to reference OCI charts as dependencies, thus breaking gardens ability to deploy them. The workaround is to simply pin the chart to the version before the dependency upgrade, but even that will eventually stop working once they stop the (old) helm index. e.g. try deploying this without the pinned version

yaml
kind: Module
type: helm
name: kafka
include: []
repo: https://charts.bitnami.com/bitnami
chart: kafka
# version: 21.4.6
values:
  maxMessageBytes: "10000000"
  persistence:
    enabled: false
  numPartitions: 10

Is there a reason why workflows can't have the command

run workflow XXX

We have one workflow specifically designed for BuildKite and it could use calling other workflow instead of having to duplicate the steps there and copying them over... I think we can all agree copying is bad, will break the single source of truth concept. Thank you.

It seems in my current setup

.garden/error.log

is always empty. However I find the actual file under

.garden/logs/error.log

Alongside

development.log

How can I fix this to not go under logs folder and just stay on the root folder. I searched the documents and I could not find a way to influence this via an env variable or some sort of config. Thank you!

Maybe this would be better as an issue on github, but it is kind of unrelated to the codebase itself. Anyways, I am starting to use the gardendev/garden-gcloud container for running garden in CI, and I've found that the gcloud application is a bit outdated even in the latest tag. Would be awesome if you could publish a version with a more up to date version. Here is the message I received when using this image:

gardendev/garden-gcloud:latest

$ gcloud --quiet components update
Beginning update. This process may take several minutes.
Your current Google Cloud CLI version is: 411.0.0
You will be upgraded to version: 428.0.0
┌─────────────────────────────────────────────────────────┐
│            These components will be updated.            │
├─────────────────────────────────┬────────────┬──────────┤
│               Name              │  Version   │   Size   │
├─────────────────────────────────┼────────────┼──────────┤
│ BigQuery Command Line Tool      │     2.0.91 │  1.6 MiB │
│ Bundled Python 3.9              │     3.9.16 │ 63.4 MiB │
│ Cloud Storage Command Line Tool │       5.23 │ 15.5 MiB │
│ Google Cloud CLI Core Libraries │ 2023.04.25 │ 20.3 MiB │
│ Google Cloud CRC32C Hash Tool   │      1.0.0 │  1.2 MiB │
│ anthoscli                       │     0.2.36 │ 68.4 MiB │
│ gcloud cli dependencies         │ 2023.04.25 │ 11.3 MiB │
│ gke-gcloud-auth-plugin          │      0.5.2 │  7.7 MiB │
│ kubectl                         │    1.24.13 │  < 1 MiB │
│ kubectl                         │    1.24.13 │ 92.6 MiB │
└─────────────────────────────────┴────────────┴──────────┘
A lot has changed since your last upgrade.  For the latest full release notes,

and so on.

Hi Garden team! We recently upgraded our CI cluster to Kubernetes 1.23, and after we upgraded, we began to see intermittent "socket hang up" errors printed from Garden, followed by an immediate termination. I'll post an example log in the thread. After doing a lot of troubleshooting and searching, we think that upgrading to Node 19+ might fix the issue. It makes some changes to networking that might fix the problem. Could ask for a favor - could you publish a pre-release build of Garden that uses Node 19 or Node 20, so we can verify? Thank you!

Is it possible to have ingress like functionality but to non ingress endpoints? (TCP/UDP) for DB and other services?

One of my coworkers has been getting the following error when running garden dev and cannot use his dev environment because of it.

/snapshot/project/tmp/pkg/cli/node_modules/execa/lib/error.js:59
        error = new Error(message);
          ^
Error: Command "git status" failed with code 128:
fatal: this operation must be run in a work tree
    at makeError (/snapshot/project/tmp/pkg/cli/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/snapshot/project/tmp/pkg/cli/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at exec (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/util/util.ts:231:17)
    at /snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/vcs/git.ts:97:26
    at wrapped.ensureSafeDirGitRepo (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/vcs/git.ts:162:7)
    at wrapped.getRepoRoot (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/vcs/git.ts:205:5)
    at wrapped.getFiles (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/vcs/git.ts:269:21)
    at findConfigPathsInPath (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/util/fs.ts:175:17)
    at /snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/watch.ts:298:29

Here is more context about our setup and about the encoutered problem: - Garden version: 0.12.55 - We include 3 remote sources in the garden.project.yaml file. - We have a deployment bash script which runs

garden link source

on those remote sources and then

garden dev

- The problem is sadly only reproducible on my coworkers MacOS laptop at the moment. I would appreciate any leads on this since it's affecting my coworker's productivity by quite a lot. 😦

Hello, Has anyone had a chance to look into: https://github.com/garden-io/garden/issues/4174

Hello, We have a task that we run on a database image that exports some artifacts. While the task is doing it's thing we get a lot of these

outputs

. It looks like it is not affecting functionality

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added to [ReadEntry]. Use emitter.setMaxListeners() to increase limit

We get about 30 - 50 of such outputs. Please find attached image.

I have a Garden Module of type container that I want to deploy with a service. I want this service to be of kubernetes ServiceType LoadBalancer instead of the default ClusterIP, but I am struggling to find a way to achieve this without specifying kubernetes manifests manually as a kubernetes Module. Is there a way to specify this? In general, it would be great if it was possible to specify arbitrary kubernetes manifest fields in the Garden Module service spec. The services field will generate both deployment, service, and ingress manifests, but perhaps it could be possible to override some defaults for these at need with f.ex

services:
  - name: blabla
    service:
      type: LoadBalancer
    deployment:
      labels:
        app: my-app
    command: /bin/bash
    ports:
      - name: http
...

Hi, I think I'm bumping into caches somewhere, but I"m not sure which ones, and I'm not sure how to proceed. I have a container-type module which references a repository:

yaml
kind: Module
type: container
name: gateway-cache
repositoryUrl: git@github.com:B612-Asteroid-Institute/gateway.git#main

services:
  # <etc>

The

gateway

repository (which is private, sorry) has a Dockerfile in it. When I

garden build

this

gateway-cache

module, I get an error. The error is from an old line in an old version of the Dockerfile - not the version currently at

HEAD

of

main

on that repo. I don't seem to be able to propagate changes from my Dockerfile to the garden build. Our Garden installation was mostly set up by other developers on my team so I don't know what other context would be helpful. We use

buildMode: cluster-buildkit

on a kubernetes cluster, if that helps. What caches are involved in

garden build

and how do I clear them or disable their use?

I'm aware of this feature, but had no luck using it as a build time dependency (we are trying to run a command locally and use it as a docker image build arg): https://docs.garden.io/using-garden/variables-and-templating#runtime-outputs Currently we have a workaround to define the command as the build command for the exec module and add the module as a build dependency to the container module. Can we achieve this without writing things to a file? Does bonsai already solve this?

I have a mongo container with some data loading tasks defined. Is there a way for the Task to 'inherit' the

env:

from the container?

In this example I can't access action outputs https://github.com/pepov/kcp-playground/blob/actionref/kcp.garden.yml#L14 Based on the docs I would expect this to work: https://docs.garden.io/v/bonsai-release/using-garden/actions#text-action-kinds

garden deploy kcp
Garden Bonsai (0.13) is in beta. Please report any issues here:
https://github.com/garden-io/garden/issues/new?labels=0.13&template=0-13-issue-template.md&title=0.13%3A+%5BBug%5D%3A
Deploy 🚀

ℹ garden                    → Running in namespace default in environment default
ℹ providers                 → Getting status...
✔ providers                 → Cached (in 2.1 sec)
ℹ providers                 → Run with --force-refresh to force a refresh of provider statuses.
ℹ graph                     → Resolving actions and modules...
✖
Error processing config for Deploy action kcp:
Invalid template string (${actions.build.kcpctl.outputs.dep…): Could not find key actions. Available keys: command, datetime, environment, git, inputs, local, parent, project, secrets, template, var and variables.

See .garden/error.log for detailed error message

Hi, i would like to know how i can influence the version of each module. Currently if i execute garden deploy every module is build new even if there was no code change. Kind regards

Is there a way I can explicitly define how to wait for certain resources within a kubernetes deploy action? (Bonsai) Garden seems to not care about completeness of Jobs and the number of running replicas in statefulsets ( for example if pods are waiting for a volume). I would like to state that my action should be considered complete based on some value in the resource's state if that is possible.

Release 0.13.0 has a breaking change, "The cert-manager integration has been removed." I was using that cert-manager integration. In particular, I used the

managedBy

key, but now

garden status

gives an error:

Error validating provider configuration: key "managedBy" is not allowed at path .tlsCertificates[0][managedBy].

I don't know how to proceed. Is there a migration guide or anything for how to safely run garden 0.13.0? Any guidance would be helpful.

After upgrading to bonsai (and changing nothing else at all), I am stuck with this error and cannot deploy at all. I tried deleting the .terraform dir and lock file, and then it got worse. I did a re-init with:

garden tools terraform.terraform-1-2-9 -- -chdir=infra init

And that worked, but garden still will not start with the below error.

Error: Configured provider 'terraform' has not been registered.    
at /snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/garden.ts:723:17    
at tryCatcher (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/util.js:16:23)    
at MappingPromiseArray._promiseFulfilled (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/map.js:68:38)    
at MappingPromiseArray.<anonymous> (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/promise_array.js:115:31)    
at MappingPromiseArray.init (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/promise_array.js:79:10)    
at MappingPromiseArray._asyncInit (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/map.js:37:10)    
at _drainQueueStep (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/async.js:97:12)    
at _drainQueue (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/async.js:86:9)    
at Async._drainQueues (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/async.js:102:5)    
at Immediate.<anonymous> (/snapshot/project/tmp/pkg/cli/node_modules/bluebird/js/release/async.js:15:14)    
at processImmediate (node:internal/timers:471:21)

Error Details:
name: terraform
availablePlugins:
  - exec
  - container
  - hadolint
  - kubernetes
  - local-kubernetes
  - octant
  - templated

I am unable to use my system at all with bonsai. The ONLY thing that has changed is the version of garden. I will try to downgrade, and I have warned my team not to upgrade. Not a fun surprise for the morning.

Wondering if anyone has had success using bonsai with persistentvolumeclaim module configs in their project. It looks like every one of ours is resulting in the error “Could not find Build action ” The goal here is to gradually migrate so ideally I won’t need to convert all volume claim modules into actions in order to get past this error.

Hi everyone, I'm experiencing port-forwarding issues on garden 0.12.49 and above (we are not ready to upgradeto Bonsai yet). On 0.12.48 I can run a simple

mysql -u root -h 127.0.0.1 -p

and successfully connect to my database. On 0.12.49 and above that command results in this error

ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (61)

I started garden in silly debug mode on each version. When connecting to mysql on 0.12.48 I see the following output from garden

ℹ mysql [debug]             → Starting port forward to mysql/mysql:3306
ℹ mysql [silly]             → Getting getPortForward handler for service mysql
ℹ mysql [silly]             → Calling getPortForward handler for service mysql
ℹ mysql [debug]             → Forwarding local port 63925 to Service/mysql port 3306
ℹ mysql [silly]             → Running 'kubectl --context=docker-desktop --namespace=localhost-demo port-forward Service/mysql 63925:3306'
ℹ mysql [silly]             → [Service/mysql port forwarder] Forwarding from 127.0.0.1:63925 -> 3306

ℹ mysql [debug]             → Successfully started port forward to mysql/mysql:3306
ℹ mysql [debug]             → Connecting to mysql/mysql:3306 port forward at localhost:63925

After upgrading to the 0.13 version of the CLI, running any command tries to update the nginx ingress controller and fails. Steps to replicate: - Running on Ubuntu 18 - Start with 0.12.56 version of garden - Create a new kind cluster (kind version is 0.17.0 - https://kind.sigs.k8s.io/) - Initialize garden resources in the cluster via

garden plugins local-kubernetes cluster-init

- Upgrade to the 0.13.0 version of the CLI - Run

garden validate

- this triggers upgrades of garden managed resources including the nginx controller Expected results: No errors and components are updated Actual results:

Resource: "batch/v1, Resource=jobs", GroupVersionKind: "batch/v1, Kind=Job"
Name: "ingress-nginx-admission-patch", Namespace: "ingress-nginx"
...TopologySpreadConstraints:[]core.TopologySpreadConstraint(nil), OS:(*core.PodOS)(nil)}}: field is immutable
...
Failed resolving one or more providers:
- local-kubernetes

Full log is attached https://cdn.discordapp.com/attachments/1111730980726775960/1111730980936482846/message.txt