v1.1.4

HelmRelease PR Checks

• Adding checks for the HelmReleases when there is an event in a PR. This will help us to make sure that the charts being merged in are syntactically correct and can be parsed by Helm template.

Inspired by:

• https://jamiemagee.co.uk/blog/how-to-host-your-helm-chart-repository-on-github/
• https://itnext.io/validating-helmreleases-in-ci-using-hrval-7a785b1c1b21

v1.1.3

Azure configurations

A fully working Flux deployment and services for Azure AKS

Includes:

• Flux
• Flux Helm Operator
• sealed-secret
• nginx-ingress
• external-dns
• prometheus-operator

v1.1.2

• Thanks @grebois for all of the AWS examples: https://github.com/ManagedKube/kubernetes-common-services/tree/master/kubernetes/flux/releases/aws/dev
• Thanks @tonyjchong for the very detailed setup guide: https://github.com/ManagedKube/kubernetes-common-services/blob/master/docs/setup-guide.md

v1.1.1

cluster-issuer helm chart

• This release is here to peg the current helm chart to a static tag

cluster-issuer version: v0.1.1

v1.1.0

This is big overhaul on the way we generate the Kubernetes yaml that Flux will apply. This structural change was necessary to make for supporting the upcoming linting and Helm chart testing that can run locally to make sure everything is working locally before pushing the code into your repository. Without this change, it would have made those future activities a lot harder to do without user intervention and the purpose of this project is really to automate away manual user activities.

Breaking changes

• In the HelmRelease's we will no longer use the valuesFrom.configMapKeyRef methods. Instead we will be using just values.

  valuesFrom:
  # Base values for all environments
  - configMapKeyRef:
      name: helmrelease-base-values
      key: base-values.yaml
      optional: false
  # This environment specific values
  - configMapKeyRef:
      name: helmrelease-env-values
      key: values.yaml
      optional: false

• Going forward, we all of the environment and base values should be in the values.

Significant changes

• kustomize will be used for base and environment specific values. Notes on why we are using kustomize: https://github.com/ManagedKube/kubernetes-common-services/blob/master/docs/kustomize.md

Required Actions

• You will need to change all of the valuesFrom.configMapKeyRef to a values format
• Add kustomize and .flux.yaml files to your Flux release directory paths.
• Examples environment: https://github.com/ManagedKube/kubernetes-common-services/tree/master/kubernetes/flux/releases

v1.0.4 - nginx-ingress Helm Chart Update

Updating nginx-ingress to Helm chart version: 1.36.0

Example usage:

• AWS: https://github.com/ManagedKube/kubernetes-common-services/blob/master/kubernetes/flux/releases/aws/dev/nginx-ingress/helmrelease-external.yaml
• GCP: https://github.com/ManagedKube/kubernetes-common-services/blob/master/kubernetes/flux/releases/gcp/dev/nginx-ingress/external/helmrelease-external.yaml

v1.0.3 - Flux Helm Operator update to 1.0.0

Updating the Flux Helm Operator to version 1.0.0.

You can apply this update right on top of the old version.

Install/Update:

• https://github.com/ManagedKube/kubernetes-common-services/tree/v1.0.3/kubernetes/helm/flux/helm-operator#install-the-helm-operator

v1.0.2 - Prometheus-operator Helm Chart Update

• Updating prometheus-operator chart to version: 8.12.12
• Upgrade notes: https://github.com/ManagedKube/kubernetes-common-services/blob/master/docs/upgrade-notes/prometheus-operator-8.12.12.md

v1.0.1 - Kubecost cluster-turndown service

Adding in Kubecost cluster-turndown service. This service helps you to turn down namespaces or nodes in a cluster on a schedule to help save you cost when you are not using it.

v1.0.0 First Release

This is the first release with a full end to end walk through on how to set this up with the suite of apps.