Welcome to the monthly product updates from Devtron.
We are excited to share monthly updates with you. Devtron’s April release is packed with powerful features and enhancements crafted by us to streamline your workflow and unlock new levels of efficiency.
What’s New
Enhanced Resource Browser
We know managing and locating specific resources within large Kubernetes clusters can be a difficult task. Primarily, it leads to inefficiencies and delays in resource management processes. The Devtron resource browser now supports powerful filtering and querying capabilities. This will enable users to locate and manage specific resources within their clusters quickly. The feature streamlines the resource management process, efficiently identifying and manipulating the desired resources across multiple clusters and namespaces.
Port Forwarding
Accessing Kubernetes clusters is a relatively complex process for developers. They had to obtain and manage the kubeconfig file that contains sensitive cluster configuration and authentication credentials. Generating, distributing, and securely handling the kubeconfig file posed significant challenges and security risks. One more major problem with these files is managing Resource Based Access Control (RBAC) for specific users.
Devtron’s new Port Forwarding feature allows developers to access Kubernetes clusters seamlessly without needing an actual kubeconfig file. By simply using the devtron proxy URL and an access token, developers can get access to the cluster, eliminating the need to obtain and manage the kubeconfig file. As an admin, this feature allows you to define precise RBAC permissions per developer in the dashboard. Their token is then scoped to those specific accesses for the target cluster. Developers gain secure, frictionless access with the right level of permissions. This streamlined approach enhances developer productivity, reduces operational overhead, and mitigates security risks associated with handling sensitive cluster credentials.
Security Vulnerability for K8s Resources
Ensuring the security of Kubernetes resources before deployment is crucial, as any vulnerabilities could potentially expose sensitive data or allow malicious attacks. Previously, before deploying applications, we scanned the application code and container images to identify potential vulnerabilities. Taking that feature to the advanced level we've introduced the Security Vulnerability Scanning for K8s Resources feature to address this concern. With this feature, users can easily enable vulnerability scanning for their Kubernetes resources like deployments. Once enabled, the feature automatically scans the specified resources and provides detailed reports highlighting any potential vulnerabilities found. Users can then review the reports and take necessary actions to address the identified vulnerabilities, ensuring their Kubernetes resources are secure.
Visibility for Application Pod Restarts
Troubleshooting application pod restart errors can be time-consuming and frustrating, requiring manual inspection of pod manifests and events to identify the root cause. To simplify the process, Devtron’s UI will now provide enhanced visibility into the reasons behind application pod restarts. Users can quickly identify the root cause of restarts, whether due to out-of-memory situations (OOMKill), code errors, or liveness probe failures, directly from the application page. This eliminates the need for manual inspection, enabling faster troubleshooting and resolution of pod restart issues.
Bug Fixes
- Fixed vulnerabilities across multiple services by updating dependencies using Dependabot.
- Implemented the use of the “helm upgrade --install” command for Helm app deployments in the NO_GITOPS mode.
- We resolved an issue causing the git sensor container to restart due to a log. Fatal error.
- Fixed a bug where some OCI repositories were not appearing in the charts store.
- We resolved an issue where applications were incorrectly showing as hibernated even when their pods were running without any problems.
- Addressed a problem where deployments would fail if a sync operation was in progress simultaneously.
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.
