Releases: gruntwork-io/helm-kubernetes-services
Releases · gruntwork-io/helm-kubernetes-services
v0.2.19
Charts affected
Description
Add support for priorityClassName in pod templates.
Special thanks
Special thanks to @reynoldsme for their contribution!
Related links
v0.2.18
Charts affected
Description
Add support for hostAliases in pod templates.
Special thanks
Special thanks to @greysond for their contribution!
Related links
v0.2.17
Charts affected
Description
Use autoscaling/v2
API in HPA for Kubernetes versions >= 1.23.
Special thanks
Special thanks to @paul-pop for their contribution!
Related links
v0.2.16
Charts affected
Description
Updated the chart to allow specifying a sub path for the volume mount for Secret
.
Related links
v0.2.15
Charts affected
Description
Update k8s-service
Helm Chart to allow configuration of traffic policies for the created K8S Service
.
Special thanks
Special thanks to @denis256 for their contribution!
Related links
v0.2.14
Charts affected
Description
Added new input parameter containerArgs
that can be used to define custom args that should be passed to the deployment spec. It behaves exactly as the containerCommand
, the only difference is that it will populate the args
instead of the command
in the spec.
Special thanks
Special thanks to @thiagosalvatore for their contribution!
Related links
v0.2.13
Charts affected
Description
Added support for configuring cluster ip on service. This will allow you to configure a headless Kubernetes service.
Related links
v0.2.12
Charts affected
Description
Fixed bug where number based service port settings on ingress
were not being interpreted correctly as number when set in values.yaml
.
Related links
v0.2.11
Charts affected
Description
Added the ability to configure session affinity on the Service
.
Special thanks
Special thanks to @tdharris for their contribution!
Related links
v0.2.10
Charts affected
Description
Added the ability to configure custom container lifecycle hooks on the Pods using the new lifecycleHooks
input value. Note that configuring a custom preStop
lifecycle hook takes precedence over the existing shutdownDelay
configuration. Refer to the input value documentation for lifecycleHooks
in the values.yaml file for more information.
Related links