Exclude Helm manifests in get-started guide

[2opremio]

The get started guide uses repo github.com/weaveworks/flux-get-started
which contains HelmRelease manifests, but the guide didn't instruct
the reader to deploy the Helm operator.

Fixes #1898

[hiddeco]

I think we should make it more clear to the user that installation of the Helm operator is optional (and only required because the flux-get-started repository makes use of it).

If the user now follows these steps, but for example, has not installed Tiller on the cluster (because we did not tell them to), the apply of the HelmRelease will succeed but the roll-out of the release itself will fail (and the operator will only be logging errors).

[2opremio]

That's true. Then, we either change the example repository to one without HelmReleases or we add instructions to install Tiller and indicate that helm is optional. Thoughts?

[2opremio]

BTW, how could the guide have possiblly ever worked? I'll do some digging

[hiddeco]

From the git log in my head; there was a commit a while ago that just changed the repository URLs without matching the content.

---

Head was right: #1527

[hiddeco]

Then, we either change the example repository to one without HelmReleases or we add instructions to install Tiller and indicate that helm is optional.

I think the latter would be good, with a note saying that for demo purposes we install the operator too (and thus Tiller must be installed) but it is fine to only make use of the Flux daemon.

[dholbach]

Hum. Maybe I'm missing something, but AFAICS the get started tutorial is about "flux standalone" (cf this note), whereas the helm get started tutorial is about helm: the need to install Tiller is discussed there.

[hiddeco]

AFAICS the get started tutorial is about "flux standalone"

Correct, the problem is that the repository linked in this doc (and used as an example) contains HelmRelease resources, confusing users (see linked issue).

[2opremio]

We can also change the repository.

…

On Fri, Apr 5, 2019, 12:06 Hidde Beydals ***@***.***> wrote: AFAICS the get started tutorial is about "flux standalone" Correct, the problem is that the repository linked in this doc (and used as an example) contains HelmRelease resources, confusing users (see linked issue). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1902 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACQOJCzeAzdeO7gHxTEkKgFp-mHEgYtzks5vdyA0gaJpZM4cdEfK> .

[dholbach]

This is unfortunate. It'd be great if we could

1. maintain just one example
2. have a straight-forward example with clear instructions that you can easily tailor to your use-cases

It looks like we can't easily have it all this time.

My inclination would be to merge this PR, but make a note that we at least document why this is necessary in the future, and even better: make the use of the example repo here more "obvious"?

[2opremio]

It looks like we can't easily have it all this time.

We can also restrict the repo to directories not including HelmReleases by configuring the flux deployment. I think I will do that.

[2opremio]

@hiddeco @dholbach PTAL

[hiddeco]

I think we got ourselves a winner 💯

[dholbach]

Thanks for the fix - this looks clean. (Even if it adds another step to the "get started" experience - I guess I'll file a separate issue about this.)

Have you tried this locally? In my case the new podinfo gets deployed, but for some reason the color does not change.

[2opremio]

In my case the new podinfo gets deployed, but for some reason the color does not change.

It does work for me. Do the logs show anything odd?

I don't see why any of the changes I made would cause flux not to update the deployment correctly.

[dholbach]

Just started with a fresh minikube, same thing. The correct revision is deployed. Colour stays green.

[2opremio]

I will take a deeper look. However I doubt that's caused by this PR. Does it work when deploying helm and the helm op?

[dholbach]

The tutorials follow different paths:

• standalone get started asks people to change PODINFO_UI_COLOR to blue in workloads/podinfo-dep.yaml - this seems not to work in either of the variants.
• helm get started asks people to update the image rev of mongodb, this works.

[dholbach]

Maybe we can just copy https://github.com/weaveworks/flux/blame/master/site/helm-get-started.md#L147 (147 and following) over to get-started.md?

[dholbach]

/cc @stefanprodan on the above

[hiddeco]

I think the podinfo application no longer listens to the PODINFO_UI_COLOR environment variable (https://github.com/stefanprodan/k8s-podinfo/search?q=PODINFO_UI_COLOR&unscoped_q=PODINFO_UI_COLOR).

Or on a second thought, it should. https://github.com/stefanprodan/k8s-podinfo/blob/7d5200a78a6206c69e761be4c8791afe9427895d/cmd/podinfo/main.go#L33

[2opremio]

Can me merge this and create a separate issue for the color?

[2opremio]

It does work for me.

I retried and it didn't, I would had sworn it did. ¯_(ツ)_/¯

Sorry @dholbach

[dholbach]

Let's copy over the Helm Get Started bits into the other tutorial in a separate issues.

[squaremo]

Is this ready to merge or is it blocked on something -- I'm not clear after reading the comments 😅

[dholbach]

Yes, let's do it, and fix the second part of it in a separate PR.