#helmfile (2019-01)

@daveyu has joined the channel

I’m trying to set container args so the spec in the deployment manifest looks like this:

    spec:
      containers:
      - args:
        - -endpoint
        - $(ES_ENDPOINT)

However, when using the monochart and specifying like this:

        deployment:
          pod:
            args:
              - -endpoint
              - $(ES_ENDPOINT)

This is the manifest that gets generated:

    spec:
      containers:
      - args:
        - -endpoint $(ES_ENDPOINT)

Any ideas?

I think there was a recent bug with this

@Andriy Knysh (Cloud Posse) was that fixed?

@Igor Rodionov

(btw, a bunch of open PRs against monochart https://github.com/cloudposse/charts/pulls)

https://github.com/cloudposse/charts/pull/185/files#diff-01b89b0376166b7fc10166b6a89c0018R49

hmm… i did not see those issues, maybe from some recent additions

looks like we only support args as a string

https://github.com/cloudposse/charts/blob/master/incubator/monochart/templates/deployment.yaml#L56

are you running the latest release?

0.9.0

we always supported args as strings, but after the latest addition from @Igor Rodionov I think it could be yaml now https://github.com/cloudposse/charts/blob/master/incubator/monochart/templates/deployment.yaml#L56

this is with 0.8.0

update to 0.9.0 and test with yaml

will do. thanks

so.. i can’t figure out how it should be as yaml

sec

My guess is this should look something like

basically, put it on a new line

Use any guy repo with Helmfile https://github.com/aslafy-z/helm-git

@Igor Rodionov

@Daren

Nice, looks like a better implementation.

yea, uses git protocol scheme so it’s compatible with all helm tools

Yep helm-git seems GREAT. I’m even considering to include it in helmfile’s docker image https://github.com/roboll/helmfile/issues/436

How about adding a “mixins” to helmfile? I need your feedback(s)! https://github.com/roboll/helmfile/issues/428#issuecomment-455055033

And also a gomplate integration for sourcing helm chart values from vault (and more in the future https://github.com/roboll/helmfile/issues/392#issuecomment-455061273

Have you ever wanted to write {{ readFile "whatever" | tpl . }} in your helmfile templates? https://github.com/roboll/helmfile/issues/420

@zadkiel has joined the channel

Hi guys, i’m struguling trying to make helmfile (helm diff) work with my git plugin

it looks like the HELM_HOME isn’t set and as the plugin uses helm cmd it fails

Error: Couldn't load repositories file (repository/repositories.yaml).
You might need to run `helm init` (or `helm init --client-only` if tiller is already installed)
Error: found in requirements.yaml, but missing in charts/ directory: webhook

within my git downloader plugin called by helm diff

I fixed it by setting up a temporary helm home in a temp file:

  HELM_HOME=$(mktemp -d)
  trap 'rm -rf "$HELM_HOME"' EXIT
  helm init --client-only --home "$HELM_HOME" 
  export HELM_HOME

Still, I can’t access to the existing repositories.

What is the error you are getting now?

No more error now, but the plugins resolves dependencies for plugin (with helm dependency update) without using the existing user repositories as I had to setup a temporary helm home

Now I hit something else,

    hooks:
    - events: ['prepare']
      command: 'kubectl'
      args: ['{{if eq .HelmfileCommand "delete"}}delete{{else}}apply{{end}}', '-f', '<https://gist.githubusercontent.com/aslafy-z/8725d10394b6f434ce0da65accfc994b/raw/fb32e659e97da5bd9a8a91dcd7e0de6d2a891b81/cert-manager-0.5.2-crd.yaml>']

gives me

error during helmfile.yaml parsing: template: stringTemplate:27:22: executing "stringTemplate" at <.HelmfileCommand>: can't evaluate field HelmfileCommand in type tmpl.TemplateData

There should be at least one more hook who triggers on a release delete

I should be able to use this kind of templating right?

@Erik Osterman (Cloud Posse) any clue?

(we are not using hooks yet…)

but i like what you’re trying to do

we could use that too…e.g. with kiam to annotate a namespce

@Igor Rodionov

I saw helmfile hooks just today

@zadkiel rather than use kubectl, have you considered using the raw chart?

https://github.com/helm/charts/tree/master/incubator/raw

Also, check out our monochart: https://github.com/cloudposse/charts/tree/master/incubator/monochart

We can deploy nearly any service without writing a helm chart

Waw that’s cool! Fits perfectly helmfile

Wouldn’t it be somewhat bloated to use a full chart just to deploy a crd? Should I add the base chart (cert-manager) and his crd as realease in a single helmfile? And then depend on this helmfile within another one?

Any idea why the templating line I send doesn’t work?

Wouldn’t it be somewhat bloated to use a full chart just to deploy a crd?

my preference is consistency

with helm, we get a history of releases/changes

we treat it like an OS package manager

prefer apk add something over tar -zvxf something.tar.gz && make -C something all install so to say

Sure, will try it! Still, any idea about the templating issue ? :/

@zadkiel Hey! I guess you need to defer template execution.

Raw template exprs like ` {{ .Foo.Bar }} ` are executed at parsing helmfile.yaml. What you need there is defer the execution of {{ .Helmfile.Command ... }} until each release is processed(which is where the hook happens).

Try using golang template comments for that.

More concretely,

{{if eq .HelmfileCommand "delete"}}delete{{else}}apply{{end}}

should be rewritte to:

"{{`{{if eq .HelmfileCommand "delete"}}delete{{else}}apply{{end}}`}}"

Gathering feedbacks on helmfile values https://github.com/roboll/helmfile/issues/430

And the upcoming Release Template feature https://github.com/roboll/helmfile/pull/439

@Igor Rodionov any opinions?

Hi guys! I finished helm-git refactor to make it more modulable and robust. It’s still pending as a PR, feel free to give an eye and throw your opinion / review: https://github.com/aslafy-z/helm-git/pull/1. Thanks!

Added a comment

Awesome work! Just added comments as well.

Thanks @mumoshu - good point

https://github.com/roboll/helmfile/blob/master/docs/writing-helmfile.md

@Igor Rodionov @joshmyers @Andriy Knysh (Cloud Posse)

layering is supported

super!

Still working on helm-git , switching from ‘@’ to ‘//’ broke helm fetch repo/chart calls. Had to revert

I’m still blocked to deploy cert-manager. I need to deploy it’s CRDs before deploying it, and apply configured CRDs resources after all.

One way simple to do that would be to accept concurrency field within helmfile.yaml so I could have a helmfile dedicated to cert-manager and apply my resources one by one

see: https://github.com/roboll/helmfile/issues/382#issuecomment-429849131

I’m looking for a tool that takes a yaml k8s resources file and convert it into a compatible value file for incubator/raw. Any idea?

Haven’t seen a tool for that

However, have you seen yq?

https://github.com/cloudposse/packages/tree/master/vendor/yq

Since you’re a total scripting ninja, you could probably munge the YAML with this tool

anyone uses requirements.yaml and requirements.lock with helmfile? welcoming your opinion on https://github.com/roboll/helmfile/issues/415#issuecomment-457097079

interested in adding a helm-tiller integration to helmfile? come to leave your comment! https://github.com/roboll/helmfile/issues/449

Ohhhhh that’s a neat idea!

@coreygale has joined the channel

@aqua has joined the channel

I’m overdue on a PR to helmfile - https://github.com/roboll/helmfile/pull/459

Thanks @Shane

We’ve wanted to do this. As a stop-gap, we’re using a namespace label in all of our releases.

https://github.com/cloudposse/helmfiles/blob/master/releases/cert-manager.yaml#L23