SweetOps #helm for December, 2020

Archive: https://archive.sweetops.com/helm/

2020-12-09

s_slack

As @Erik Osterman (Cloud Posse) suggested, not sure if anyone has any experience with this ->https://sweetops.slack.com/archives/CQCDCLA1M/p1607475676220800

Just wondering if anyone has any insight on how to efficiently manage configuration in micro-services environment where each service/repo has its own helm configuration values. So if you need to support countryA on serviceA but not on countryB then you can configure in serviceA repo only. But this scales very poorly with hundreds of services. Is there any way to manage this when each service is maintained by specific teams.

2020-12-10

wannafly37

09:26:09 PM

I’m trying to read an HTML file in and include it in a string as an annotation but having a difficult time due to what I assume is quotes/single quotes. Anyone done this before? Basically I’m including a static maintenance page as a ALB rule

Erik Osterman (Cloud Posse)

08:04:37 PM

https://rollout.io/blog/yaml-tutorial-everything-you-need-get-started/

YAML Tutorial: Everything You Need to Get Started - Rollout Blog

YAML Ain’t Markup Language (YAML) has a risen in popularity over the past few years. Here’s a YAML tutorial to get you started quickly.

Erik Osterman (Cloud Posse)

08:04:45 PM

Look into multi-line values

Erik Osterman (Cloud Posse)

08:04:57 PM

bar: |-
  this is not a normal string it
  spans more than
  one line
  see?

Erik Osterman (Cloud Posse)

08:05:18 PM

(almost like YAML HEREDOC)

wannafly37

07:43:38 PM

Thanks, Erik. I figured it out but it was definitely some line break/quoting problems - ended up having to take all double quotes and line breaks out of the HTML

2020-12-11

2020-12-12

zeid.derhally

11:26:21 AM

We have a 3rd party helm chart that we are working with. it is an umbrella chart that has other umbrella charts. Probably like 3 levels of charts…many of the settings from the subcharts are not exposed in the root values.yaml. Was looking for a tool/script that will generate a values.yaml with all the values from subcharts

2020-12-14

2020-12-18

Joaquin Menchaca

12:30:46 AM

Is there a way to see the badly rendered values, so I can see where I made the mistake?

Error: YAML parse error on dgraph-lambda/templates/deployment.yaml: error converting YAML to JSON: yaml: line 34: did not find expected key
helm.go:81: [debug] error converting YAML to JSON: yaml: line 34: did not find expected key
YAML parse error on dgraph-lambda/templates/deployment.yaml
...

Doesn’t help. I want to see how it was rendered so that I know how to fix it. Sometimes it’s just a matter of indentation.

Joaquin Menchaca

12:32:00 AM

And it was… grrr… this is such a frustrating part of helm, makes it so painful to debug.

2020-12-21

Joaquin Menchaca

12:28:48 AM

I’m not sure how to get this to work:

{{- if .Values.script.enabled -}}
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ include "dgraph-lambda.fullname" . }}-config
  labels:
    {{- include "dgraph-lambda.labels" . | nindent 4 }}
data:
  script.js: {{ .Values.script.script }}
{{- end -}}

This get me:

[ERROR] templates/config.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 13: mapping values are not allowed in this context

2020-12-22

bradym

09:40:19 PM

The --debug flag should show you the bad yaml.