The OCI DevOps Deploy service is excited to announce support for the latest Helm client versions: Helm 3.16.4 and Helm 3.17.0. These releases bring important updates, feature enhancements, and security improvements that will benefit users deploying applications via Helm on Oracle Kubernetes Engine (OKE) and other Kubernetes environments.

What’s New in Helm 3.16.4 and 3.17.0?

Helm 3.16.4 (Patch Release)

Helm 3.16.4 primarily includes bug fixes and dependency updates, ensuring better stability and security. Key highlights:

• Security Updates: Upgraded golang.org/x/crypto dependency from 0.30.0 to 0.31.0.

• Kubernetes Dependency Updates: Various k8s.io dependencies were updated for improved compatibility.

• Cluster Compatibility: Helm 3.16.4 is used for Kubernetes cluster version 1.28.
  
  
  
   

Helm 3.17.0 (Feature Release)

Helm 3.17.0 introduces several new features that enhance usability, security, and flexibility. Key enhancements include:

• Metadata Improvements: Annotations and dependencies are now included in chart metadata outputs, making it easier to track dependencies.

• SDK Enhancements: Authorizer and registry configurations are now customizable, providing more flexibility.

• Configuration Simplifications: The Kubernetes configuration file permissions check has been removed for a smoother experience.

• Template Functionality: Introduced toYamlPretty, a new template function for improved YAML formatting.

• Cluster Compatibility: Helm 3.17.0 is used for Kubernetes cluster versions 1.29 and above.
  
  

New Feature Examples

Using toYamlPretty for Improved YAML Formatting

The new toYamlPretty function enhances YAML formatting in Helm templates, making it more readable.

Example Usage

apiVersion: v1
    kind: ConfigMap
    metadata:
      name: my-config
    data:
      config.yaml: |-
        {{ .Values.config | toYamlPretty }}

Comparison: toYaml vs toYamlPretty

Given the following values in your values.yaml:

config:
      database:
        user: admin
        password: secret
      server:
        port: 8080
        host: "localhost"

Using toYaml:

database:
      password: secret
      user: admin
    server:
      host: localhost
      port: 8080

Using toYamlPretty:

database:
      user: admin
      password: secret
    
    server:
      host: localhost
      port: 8080

The difference is that toYamlPretty adds better spacing, making it easier to read.

OCI DevOps Deploy Integration

With these updates, OCI DevOps Deploy ensures that users can seamlessly deploy and manage their Helm-based applications with the latest tools and enhancements. Deploying to OCI’s managed Kubernetes service (OKE) using the latest Helm client versions help streamline your DevOps workflows.

Getting Started

To take advantage of these new Helm versions in OCI DevOps Deploy:

• Ensure your deployment pipelines reference Helm 3.16.4 for Kubernetes 1.28 or Helm 3.17.0 for Kubernetes 1.29 and above.
• Verify compatibility with your existing Helm charts and Kubernetes environment.
   

The OCI DevOps Deploy service remains committed to providing the latest tooling and enhancements for a seamless Kubernetes deployment experience. With the inclusion of Helm 3.16.4 and 3.17.0, users gain access to cutting-edge features, improved security, and greater flexibility in managing Helm releases.

Start leveraging the latest Helm versions in your OCI DevOps Deploy workflows today and experience enhanced performance and reliability!