devtron

Product Updates: July 2024

TL;DR: Devtron introduces Change CI for seamless pipeline switching, Pod/Cluster Terminal file downloads, and multi-arch build caching, alongside improved GitLab support, Keda hibernation compatibility and release track application management.

a month ago   •   4 min read

By Bhushan Nemade
Table of contents

Welcome to the monthly product updates from Devtron.

We are all excited to share monthly updates with you. Devtron’s July release is packed with powerful features and enhancements we crafted to streamline your workflow and unlock new levels of efficiency.

What’s New

Boost Your Debugging Efficiency: Download Files from your Pod/Cluster Terminal

While debugging Kubernetes clusters or Kubernetes pods the process needs us to exec into the container and execute some commands for troubleshooting. Once the issues have been fixed sometimes there’s a need for downloading Log files, Configurations files, and Diagnostic outputs. This feature of Devtron aims to provide built-in support in the Kubernetes cluster and Pod terminal to download the target files from the cluster and pod terminal to your local system.

download file/folder from terminal
[Fig. 1] download file/folder from terminal

Change CI: Change Your CI Pipeline with a Click

The flexibility to adapt CI processes as projects evolve is crucial for maintaining efficient and effective development workflows. Teams often need to switch between different CI tools, integrate with external systems, or optimize their pipelines without disrupting ongoing work. This adaptability becomes essential while scaling services. To address these needs, Devtron introduces the new Change CI feature. With this feature, you can seamlessly switch between different CI pipeline types, such as converting a Devtron CI pipeline to an external CI pipeline, transforming it into a CI job pipeline or linked CI pipeline, and transitioning between any pipeline type in any direction. The Change CI feature allows you to seamlessly transition between different pipeline types without disrupting your existing processes, also it ensures your development process remains agile and responsive to changing requirements, ultimately improving teams productivity.

Change-ci
[Fig. 2] Change-ci

Caching Multi-arc Builds

Application build times are a significant factor in slowing down the software development lifecycle. When dealing with multi-architecture images, these build times increase further. To address this issue, Devtron has implemented a caching mechanism. This feature allows you to build multi-architecture images in reduced time, thereby accelerating your software development lifecycle.

What has Improved

PR/Tag Source Type for CI Pipelines

Previously, the support for Pull Requests (PRs) or Tags as source types for CI pipelines was limited to GitHub and Bitbucket. With a recent enhancement, Devtron has added GitLab support, now users will be able to utilize Pull Requests (PRs) or Tags as source types for CI pipelines across all three platforms: GitHub, Bitbucket, and GitLab. This enhancement provides greater flexibility and integration options for teams using GitLab in their development workflow.

Support for Handling Hibernation and Un-Hibernation while Keda is Active

Introducing enhanced hibernation and un-hibernation support for Devtron applications while autoscaler like Keda is enabled. This feature addresses the limitation where apps using Keda dynamic scaling capabilities can't be hibernated or un-hibernated manually when needed. The enhancement will allow seamless hibernation and un-hibernation of these apps, maintaining compatibility with autoscaler.

Define applications in the Release Track

During the new software release, there can be some applications/services that should be included in each new release, this enhancement targets this specific requirement where you will be able to define specific applications in the release track that should be included in upcoming releases. Along with this you can also mark them as mandatory. If the defined application/service in the release track is marked as mandatory, each upcoming release will have that application/service. In some cases, if the application/service is not required, dropping from to release should be marked as not mandatory from the release track.

Bug Fixes

  • There was a delay in initiating the deployment in some cases, and it has been resolved.
  • The custom chart dependencies are now correctly retained during deployment
  • The issue of not getting the proper release name in the compare mode of the Helm chart is resolved.
  • Minor anomalies for the ‘build and deploy’ and ‘admin’ access for applications have been resolved.
  • Fixed a bug where reports were not visible for artifacts within jobs
  • Fixed a bug where comparison values diff for deployment template are not shown on change of selected template option
  • Fixed a bug where ReplicaCount remains unchanged after disabling the Horizontal Pod Autoscaler (HPA) in non-GitOps mode
  • Fixed an issue where Docker Builds failed when the build args have single quoted values
  • Fixed a bug when users were unable to get notifications during deployment
  • Fixed an issue where deployment is stuck in starting for no-gitops-based pipelines

Catch up on previous Devtron product updates to see what you’ve missed:

If you have any queries, don't hesitate to connect with us. Join the lively discussions and shared knowledge in our actively growing Discord Community. If you like what Devtron is solving, please give it a ⭐️ on GitHub.

Spread the word

Keep reading