toYaml | json to yaml serializer | JSON Processing library

It's not possible to use template code in values.yaml files. But you can merge several values.yaml files to reuse configuration values.

main-values.yaml

I see two issues in the code as written. Go templates produce text output, so you don't need to call toYaml on them. Also, when you call indent, it doesn't know about the indentation of the current line, so if you're going to indent something the {{ ... }} template expression usually needs to be on an unindented line.

The call itself, for example, should look like:

The nindent function is the same as the indent function, but prepends a new line to the beginning of the string.

refer : https://helm.sh/docs/chart_template_guide/function_list/#nindent

You should use indent instead of nindent, to avoid new line after spec:

As @Ramanichandran mentioned in comment section problem is solved by adding a missing value in first line in the ingress yaml. Line should look like: .Values.guacamole.ingress.enabled. The guacamole value was missed to add.

This new line after ports: shouldn't cause any errors, but you can easily get rid of it with just one modification to your template.

Instead of:

I tried to debug the helm chart using the following command:

If you want to be sure your pod/deployment won't consume more than 1.0Gi of memory then setting that MemoryLimit will do job just fine.

Once you set that limits and your container exceed it it becomes a potential candidate for termination. If it continues to consume memory beyond its limit, the Container will be terminated. If a terminated Container can be restarted, kubelet restarts it, as with any other type of runtime container failure.

For more readying please visit section exceeding a container's memory limit

Moving on if you wish to scale your deployment based on requests you would require to have custom metrics to be provided by external adapter such as prometheus. Horizontal pod autoascaler natively provides you scaling based only on CPU and Memory (based on the metrics from metrics server).

The adapter documents provides you walkthrough how to configure it with Kubernetes API and HPA. The list of other adapters can be found here.

Then you can scale your deployment based on the http_requests metric as showed here or request-per-seconds as described here.

You can define the additional set of annotations as a named template, that emits key: value pairs, aligned at the first column.

Does not appear to be supported from what I can find of their code. It would appear they just shell out to helm upgrade, would need to use the --wait mode.