Expose more configuration through values.yaml files

[jonstacks]

What

This bumps the helm chart version and allows for changing more configuration values by overwriting the values.yaml or supplying --sets when installing/upgrading.

How

• Changed the template that generates the full image path to consider global.imageRegistry. This makes it easier to use a private image registry for all images.
• Exposed frontend configuration for fullstory, openreplay, storytime, and whether or not it is a demo.
• Allow for changing log level independently for scheduler and server.
• The helm chart can now be used to deploy different versions of Airbyte without having to bump the .Chart.appVersion and releasing a new version of the chart. To do this, you can override the values.yaml when installing with a partial like so:

version: 0.29.22-alpha
webapp:
  image:
    tag: 0.29.22-alpha
server:
  image:
    tag: 0.29.22-alpha
scheduler:
  image:
    tag: 0.29.22-alpha

Its a little verbose, but it allows changing all values independently if testing different configurations is desired.

[marcosmarxm]

@jonstacks we use bumpversion to change version in files. Not sure, but can we add the chart files to automatically change using bumpversion?

airbyte/.bumpversion.cfg

Line 21 in a6c48dc

[bumpversion:file:kube/overlays/stable/kustomization.yaml]

[jonstacks]

@marcosmarxm, sounds like a great idea to me. I will look into it!

[davinchia]

Looks good, just some comments for my understanding.

[davinchia]

curious: what does this default to?

[jonstacks]

Having global.imageRegistry: "" will use dockerhub.

Example of the image generated using the default:

helm template airbyte . -s templates/scheduler/deployment.yaml | grep "image:" 
        image: airbyte/scheduler:0.29.21-alpha

Example of overriding this to use a private registry:

helm template airbyte . --set global.imageRegistry="my.docker.registry" -s templates/scheduler/deployment.yaml | grep "image:"
        image: my.docker.registry/airbyte/scheduler:0.29.21-alpha

[davinchia]

why change this to use include instead?

[davinchia]

ah is this using the custom functions defined in _helpers.tpl?

[jonstacks]

Yeah. I'm using a helper function from the bitnami common library chart to make it easier to support global.imageRegistry. Doing that in the helpers makes the main template a bit more readable IMO.

[TSkrebe]

app.kubernetes.io/version labels are currently following Chart.appVersion. Shouldn't they follow Values.version if it's defined?