garden deploycommand. You can also delete services with the
garden delete servicecommand. And you can get service logs with the
The following is specific to the Kubernetes providers.
portfor a given service, other services from inside the cluster can reach it. By default, it's reachable from
ingress, your can reach your service from outside the cluster. For example by using the
garden callcommand or with
http://demo-project.local.app.garden/<ingress-name>. You can override this by setting a
servicePortis set to
80, the default port. This is so that we can call the service directly from within the cluster with
containerPort(the port that the process inside the container is listening on) is set to
hostnameso that the full path becomes:
backendservice which means it won't be deployed until the
backendservice has been deployed and is responding to health checks. This also means that the service gets re-deployed on changes to the backend.
disabled: truein the service configuration. You can also disable them conditionally using template strings. For example, to disable a
containermodule service for a specific environment, you could do something like this: