0.24.0 Delete `lamp`, `remotecv` and `kube2iam-kops` charts

what

• Delete lamp, remotecv and kube2iam-kops charts (for now)

why

• It's outdated (from 2017)
• mysql is no longer available in https://kubernetes-charts.storage.googleapis.com, which throws this error when building the charts

Error: found in Chart.yaml, but missing in charts/ directory: mysql
helm.go:84: [debug] found in Chart.yaml, but missing in charts/ directory: mysql

• lamp needs to be updated to a newer version, e.g. from https://artifacthub.io/packages/helm/bitnami/mysql

0.23.0 Adds ability to use secretKeyRef in env spec

what

Adds the ability to use the secretKeyRef style of adding environment variables to kubernetes specs.

why

While this is already provided via envFrom in this chart, and the corresponding kubernetes features, envFrom doesn't allow you to specify the target environment variable name in your pods, nor does it allow you to use keys in your secrets that aren't valid environment variable names.

reference

• https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets-as-environment-variables

example

Providing this value:

        envFromSecretKeyRef:
          - name: CELERY_BROKER_USERNAME
            secret: example-rabbitmq-default-user
            key: username
          - name: CELERY_BROKER_PASSWORD
            secret: example-rabbitmq-default-user
            key: password

Would add the following to the template:

        env:
          - name: CELERY_BROKER_USERNAME
            valueFrom:
              secretKeyRef:
                name: example-rabbitmq-default-user
                key: username
          - name: CELERY_BROKER_PASSWORD
            valueFrom:
              secretKeyRef:
                name: example-rabbitmq-default-user
                key: password

0.22.0 [monochart] default ports

What

• Remove port default values

Why

• Whilst this is a good default it makes it hard to add your own custom name, as port duplication is possible

0.21.0 [monochart] Add `envFromFieldRefFieldPath` config

what

• [monochart] Add envFromFieldRefFieldPath config

why

• To be able to declare ENV vars from pod fields
• Example usage is Datadog APM to declare dynamic ENV var DD_AGENT_HOST from pod field status.hostIP

references

• https://docs.datadoghq.com/agent/kubernetes/apm/?tab=helm
• https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#use-pod-fields-as-values-for-environment-variables

0.20.3

[monochart] Apply earlier fix for Job to same bug in CronJob

0.20.2

Fix bugs, remove dependency on obsolescent Kubernetes repo (#256)

0.20.1: [fluentd-kubernetes-aws] Fix syntax error

[fluentd-kubernetes-aws] Fix syntax error (#255)

0.20.0 [monochart] Update `envFrom`

what

• Update envFrom section in _helpers.tpl

why

• envFrom is a list of EnvFromSource and there could be only one envFrom in a Container spec (possibly with many configMapRef and secretRef parameters)
• The current implementation creates two envFrom sections, which is not correct behavior and will fail if we use these two configs at the same time:

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

and

secrets:
  default:
    enabled: true
    mountPath: /secret-default
    annotations:
      test.secret.annotation: value
    labels:
      test_label: value
    env:
      SECRET_ENV_NAME: ENV_VALUE
    files:
      secret.test.txt: |-
        some text

• This update puts all configMapRef and secretRef parameters into just one envFrom section

0.19.0: Use GitHub actions (#250)

* use github actions

* add github workflow

* drop slash

* Fix image

* specify dir

* deploy charts to S3

* Update CURRENT_REPO_URL

* rename env

* fix env

* use github.ref instead

* use phony targets

* upgrade build-harness

* handle chart repos

* add tests

* augment tests

* only attempt to publish charts from cloudposse

* update conditional

* change entrypoint

* refactor tests

* deprecate travis

0.18.0

[fluentd-kubernetes] add serviceaccount (#247)