Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Helm: support FHRs that mention more than one image #1180

Merged
merged 3 commits into from
Jul 2, 2018

Conversation

squaremo
Copy link
Member

kubeyaml 0.3.2 supports updating the images in a FluxHelmRelease when they are given in the format:

spec:
  values:
    somename:
      image: repo/image:tag
    othername:
      image: repo/image:tag

This PR bumps the version of kubeyaml in the two places it's mentioned -- the docker file, and the shim script -- and adds a test that the update code, invoking kubeyaml actually does update an FHR given in that format.

It also adapts kubernetes/resource and kubernetes/ so that the internal model of resources in the repo and in the cluster understand how to interpret FHRs in the same way as kubeyaml does.

Fixes #1175.

squaremo added 3 commits June 28, 2018 13:45
kubeyaml 0.3.2 supports updating the images in a FluxHelmRelease when
they are given in the format:

```
somename:
  image: repo/image:tag
othername:
  image: repo/image:tag
```

This commit bumps the version of kubeyaml in the two places it's
mentioned -- the docker file, and the shim script -- and adds a test
that it actually does update an FHR given in that format.
We still have largely parallel models of things that are resources in
the cluster, and things that are defined in the git repo. Both models
need to be able to interpret FluxHelmRelease values in terms of
containers.

Because it's the same type (map[string]interface{}) being interpreted
in both places, we can write one procedure to do the interpretation,
and just use the interpretation in different ways. So: factor out a
visitor-style procedure, and use it for cluster and repo resources.
@squaremo squaremo requested a review from aaron7 June 28, 2018 16:58
@squaremo squaremo merged commit b111683 into master Jul 2, 2018
@squaremo squaremo deleted the issue/1175-fhr-support-more-images-specs branch July 2, 2018 15:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants