0.17.0 [monochart] Update to k8s 1.16

What

• Update monochart so that it is compatible with k8s 1.16

Why

• Beta APIs were promoted to different API versions

[monochart] Make serviceAccountName optional

0.16.1

Bump chart version for serviceAccountName fix (#242)

0.16.0 upgrade superset to 0.35.2

upgrade superset to 0.35.2 (#240)

* upgrade superset to 0.35.2

* version bump

[fluentd-kubernetes-aws] Change metrics names and improve alerts by introducing absent checks

What

• Reflect new metric names in alerts
• Added checks for absent metrics
• Change job to match servicemonitor configured

Why

• Alerts were monitoring nonexistent metrics so they would never be triggered

0.14.1 [monochart] Update chart version

what

• [monochart] Update chart version

why

• New features were added in the previous PR, but the chart version was not updated

references

• #235

0.14.0 [monochart] Add `serviceAccountName` attribute

what

• [monochart] Add serviceAccountName attribute

why

• To be able to provide an existing service account for pods (instead of using the default one)

0.13.1 [monochart] Update `envFrom` section

what

• [monochart] Update envFrom section

why

• Fix formatting. The generated YAML looked like this before:

 env:
+         envFrom:- secretRef:
+             name: GOCAL_SECRET_1

• Missed the conditional check and envFrom attribute

{{- if $root.Values.envFrom }}
envFrom:

0.13.0 [monochart] Add `envFrom` section

what

• [monochart] Add envFrom section

why

• Allow converting existing Kubernetes secrets and config maps (without creating them) into ENV variables in pods that in turn can be accessed by the applications running in the pods

envFrom:
  secrets: 
   - secret-1
   - secret-2
  configMaps:
   - config-1
   - config-2

0.12.0 [nginx-default-backend] Add `selector` to `Deployment`

what

• [nginx-default-backend] Add selector to Deployment

why

• Newer Kubernetes versions require selector to be present in DeploymentSpec
• Otherwise, the following error is thrown:

failed processing release ingress-backend: helm exited with status 1:
  Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Deployment.spec): missing required field "selector" in io.k8s.api.apps.v1.DeploymentSpec

references

• https://stackoverflow.com/questions/59369174/unable-to-helm-install-due-to-deployment-manifest-issue

0.11.1

Add hostAliases to the various resource specs (#218)