#helmfile - August 2019 | Slack Archive

71 messages

Questions and discussion around helmfile https://github.com/roboll/helmfile and https://github.com/cloudposse/helmfiles
Archive: https://archive.sweetops.com/helmfile/

Jul 2019

August 2019

Sep 2019

agalmost 7 years ago

are you only able to pull .Environment.Values into a values.yaml.gotmpl?

agalmost 7 years ago

like something like this doesnt work

agalmost 7 years ago

      "<http://service.beta.kubernetes.io/aws-load-balancer-ssl-cert|service.beta.kubernetes.io/aws-load-balancer-ssl-cert>": {{  .Values.cert.arn }}

agalmost 7 years ago

if my values: is setup like

agalmost 7 years ago

    values:
    - ../../values/kube2iam/values.yaml.gotmpl
    - ../../values/kube2iam/{{ .Environment.Name }}.values.yaml

agalmost 7 years ago

values.yaml.gotmpl contains the .Values.cert.arn and environment.values.yaml has an entry like

agalmost 7 years ago(edited)

cert.arn: "fdjklfsj"

agalmost 7 years ago

there is no way to reference that value from another values template

agalmost 7 years ago

or would i need to do some {{ readFile }} magic

mumoshualmost 7 years ago

@ag Hey! Yeah, you need readFile magic, or leverage sub-helmfiles like https://github.com/roboll/helmfile/issues/756#issuecomment-514013382

Helmfile values and chart(release) values are completely different things

mumoshualmost 7 years ago

@ag We're discussing about setting values from a template rendered in a custom context(=.Values)

https://github.com/roboll/helmfile/issues/745#issuecomment-510737741


releases:
- name: myapp`
  chart: my-chart
  valuesFrom:
  - templateFile:
      path: values/values-file.yaml.gotmpl
      valuesFrom:
      # Instead of implicitly passing helmfile's Values to the values-file.yaml.gotmpl
      # Overrides it with `releaseName: myapp`
      - inlineTemplate:
          releaseName: `{{.Release.Name}}` #<- you'll need {{` `}} to defer rendering until the evaluation time of inlineTemplate. otherwise this fails due to that .Release.Name isn't available at loading-time of your helmfile.yaml :)

Yevhenii Demchenkoalmost 7 years ago(edited)

Hi guys,
I'm having troubles with installing chart via helmfile.
helfile


repositories:
- name: stable
  url: <https://kubernetes-charts.storage.googleapis.com>
- name: helm
  url: <utl>
  username: <username>
  password: <password>

helmDefaults:
  tillerNamespace: kube-system
  verify: true
  wait: true
  timeout: 600
  recreatePods: true
  force: true
  tls: false

# The desired states of Helm releases.
#
# Helmfile runs various helm commands to converge the current state in the live cluster to the desired state defined here.
releases:
  - name: consul
    namespace: default
    chart: helm/consul
    version: 0.8.1
    values:
    - charts/chart-consul/values.yaml

I'm getting an error Error: failed to download "helm/consul" (hint: running helm repo update may help)
If I try to install via helm, everything works fine.
When tracing, I found out that helm tries to download tgz.pov chart file, while in index.yaml there is only tgz one.
Any ideas?

mumoshualmost 7 years ago

Interesting. How a successful helm command look like?
Can you compare it with the helm command being run by Helmfile if you run helmfile --log-level=debug?

Yevhenii Demchenkoalmost 7 years ago

successful via helm - https://gist.github.com/djackyn/725ac0638c33c89a3cb903d03707f43c
failure via helmfile - https://gist.github.com/djackyn/725ac0638c33c89a3cb903d03707f43c

Yevhenii Demchenkoalmost 7 years ago

will try to run same command as helmfile now

Yevhenii Demchenkoalmost 7 years ago

Okay, have the same problems. Seems like a bug in the helm, will check. Thanks for the direction

Nelson Jeppesenalmost 7 years ago(edited)

If I do the following:
1. deploy a chart (deployment) with helmfile
2. edit that deployment with kubectl

should a helmfile diff show a change?

Nelson Jeppesenalmost 7 years ago(edited)

Because when I run helmfile diff with a manual edited deployment, it shows no changes. This is with helmfile 0.80.2 and tested with helm 2.13.1, 2.14.1 and 2.14.3

Erik Osterman (Cloud Posse)almost 7 years ago

yes, it should, however helmfile just calls out to helm-diff https://github.com/databus23/helm-diff

mumoshualmost 7 years ago

as far as i understand, helm diff doesn't show diff for actual k8s resources

mumoshualmost 7 years ago

helm persists the desired state of k8s manifests per each helm release in a release configmap/secret in tiller namespace

mumoshualmost 7 years ago

helm-diff shows diffs from that, not from the current state of your cluster

Erik Osterman (Cloud Posse)almost 7 years ago

aha, wow, didn't know that.

mumoshualmost 7 years ago

so the downside of helm-diff is that you cant use it to detect "skews" due to manual changes

mumoshualmost 7 years ago

fyi: https://github.com/databus23/helm-diff/blob/28e683213d7c98a16a098dd21bc51f60a25f714b/cmd/release.go#L94-L99

mumoshualmost 7 years ago

i wonder if kubectl diff is useful in that case though 🤔

maybe it can be used like this:


helm get $YOUR_RELEASE_NAME --template {{.Release.Manifest}} | kubectl diff -f -

Jeremy G (Cloud Posse)almost 7 years ago

Yes, I recently encountered this behavior. helm diff diffs the new desired state against the old desired state. It is blind to manual changes in the state. I didn't even know kubectl diff existed.

Nelson Jeppesenalmost 7 years ago

Thank ya'll, that's very helpful. I was not aware of kubectl diff either.

Nelson Jeppesenalmost 7 years ago

Guess I need to keep some hands out of the kubectl pot in the future 🙂

Nelson Jeppesenalmost 7 years ago

darn, can't use kubectl diff with k8s 1.11 it seems