Skip to content

Releases: gruntwork-io/helm-kubernetes-services

v0.2.9

17 Dec 14:57
eb6959d
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Fixed bug where Ingress resources mismatch the networking.k8s.io/v1 API spec, affecting installs to k8s 1.19.

Related links

v0.2.8

06 Dec 18:26
650ef1e
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Updated the chart to allow specifying a sub path for the volume mount for ConfigMap.

Special thanks

Special thanks to @bobalong79 for their contribution!

Related links

v0.2.7

06 Dec 16:20
87a5cb7
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Updated the chart to use capabilities introspection to ensure the right API version is used for Ingress and PodDisruptionBudget resources based on the target kubernetes cluster version.

Related links

v0.2.6

16 Sep 20:18
85e7c93
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Added ability to configure terminationGracePeriodSeconds.

Special thanks

Special thanks to @martinhutton and @meganjohn for their contribution!

Related links

v0.2.5

07 Sep 16:05
63e9905
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Added ability to configure emptyDirs that are backed by the worker node disk, rather than tmpfs.

Special thanks

Special thanks to @jonnymatts-global for their contribution!

Related links

v0.2.4

25 Aug 20:47
2244a55
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Added ability to configure initContainers on the Deployment using the new input initContainers.

Special thanks

Special thanks to @davidlivingrooms for their contribution!

Related links

v0.2.3

23 Jul 21:30
cb199b7
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Updated configMaps and secrets to support injecting with envFrom so that all keys are automatically loaded as environment variables.

Special thanks

Special thanks to @ralucas for their contribution!

Related links

v0.2.2

04 Jun 18:34
0fa76db
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

You can now override the fullname that appears in the resources managed by the k8s-service helm chart using the fullnameOverride input variable.

Special thanks

Special thanks to @ralucas for their contribution!

Related links

v0.2.1

02 Jun 17:54
db95ee5
Compare
Choose a tag to compare

Charts affected

  • k8s-service

Description

Add support for overriding the deployment strategy using the new deploymentStrategy input variable.

Special thanks

Special thanks to @amirha97 and @MaxKam for their contribution!

Related links

v0.2.0

25 May 16:28
f45df6d
Compare
Choose a tag to compare

Charts affected

  • k8s-service [BACKWARD INCOMPATIBLE]

Description

The aws.irsa configuration has been deprecated and removed. Please use IRSA annotations on the Service Account. See the migration guide for more details.

Migration guide

This release deprecates the aws input value which was originally used for configuring AWS IAM Roles for Service Accounts using manual injection of the projected token (via environment variables and secrets mounting in the Pod). In newer versions of EKS, you can instead rely on the mutating admission hook that comes with every EKS cluster. To use the mutating admission hook, you need to apply the annotation eks.amazonaws.com/role-arn on the ServiceAccount.

Since the old approach of manually projecting the tokens is deprecated by AWS, this release removes the manual projection of tokens via the aws input value. If you were relying on the aws.irsa input value, you must instead switch to using the annotation on the Service Account:

serviceAccount:
  name: "my-app"
  create: true
  annotations:
    eks.amazonaws.com/role-arn: "IAM_ROLE_ARN"

Related links