Microclimate 19.02 is now available for download and was released on February 8th, 2019. Read on to learn more about what’s new in this month’s Microclimate release.
After lots of hard work over the last several months, Microclimate is now officially recognized as an IBM Cloud Pak. What is an IBM Cloud Pak? IBM uses IBM Cloud Paks as a way to designate software as trusted, enterprise-grade, and fully integrated with or supported by the IBM Cloud platforms. IBM Cloud Paks are packaged as easily consumable deployment units through the IBM Helm catalog and are deployable as Helm charts to the IBM Cloud platform, including IBM Cloud Private.
The official Cloud Pak page states that Cloud Paks “accelerate time to production and improve enterprise readiness.” Cloud Paks also provide answers to these questions:
A: Yes, they are! Microclimate scans and remediates container image vulnerabilities, uses the minimum required privileges, documents the required privileges of its containers, and provides monthly updates.
A: Along with other Cloud Paks, Microclimate is available directly from the IBM Helm catalog either by web console or CLI. The Helm chart docs include detailed instructions on installation.
A: Yes, Microclimate is available for the most recent versions of IBM Cloud Private, and each chart lists the supported versions. Likewise, we aim to ship day-and-date with new IBM Cloud Private releases.
A: Applications developed in Microclimate on IBM Cloud Private are deployed as Kubernetes applications through Helm charts. Therefore, both Microclimate applications and Microclimate itself are fully integrated with IBM Cloud Private services, such as logging, monitoring, accessing the console web UI, and more.
Although previous versions of Microclimate hit most if not all of these bullet points, it is nice to officially join the Cloud Pak ecosystem. But don’t worry if you already use Microclimate. Availability as a Cloud Pak doesn’t change how you use or install the product. If you already have a favored way of installing Microclimate, whether by the local .zip file download, by IBM Cloud Private Helm CLI, or through the IBM Cloud Private Web console, you can continue to install as you have before.
From its very first release, Microclimate has included integrated load testing and performance monitoring, including monitoring of CPU usage, memory/heap usage, HTTP incoming/outgoing requests, response times per endpoint, and flame graphs. You can find the data in the Monitor tab of the Microclimate browser UI, but wouldn’t it be cool if the Microclimate UI called out “hot” methods in the code editor itself?
With the latest release of Microclimate, you can see methods that are identified as computationally intensive when you edit your code. The browser-based code editor annotates directly alongside the offending method’s source code:
To try out this feature, first kick off a load test and then wait for it to complete. Next, open the source code that you suspect is computationally expensive, and you will now see a method annotation identifying the relative performance of these methods. More information on these features is available in our documentation at Editing your project.
New versions of Microclimate Developer Tools for Eclipse and Visual Studio Code (VS Code) also shipped with this Microclimate release. In addition to bug fixes for Microclimate Developer Tools for VS Code and Developer Tools for Eclipse, the Microclimate Eclipse Tools can be used to start a debug session for Node.js projects with the session hosted in a Chromium-based browser:
Node.js debugging was first delivered in the January Microclimate VS Code extension, and now we have reached feature parity between the two versions. You can use the development environment in which you are most comfortable while still taking advantage of everything Microclimate has to offer.
If a picture is worth one thousand words, then what is a video worth? 😄 Along with updated videos on the home page, the following new videos are available for your viewing pleasure:
These videos are a great place to start if you’re first diving into the Microclimate Developer Tools, the DevOps pipeline, or targeting IKS from Microclimate.
To round things off this month, this release includes IBM Cloud Private V3.1.2 support and a few nice quality-of-life improvements:
global.useSecurityContext=falsewhen installing the Microclimate chart.
Templates, which you can use to add more development languages and sample projects to Microclimate, can now be deleted through the web UI:
You can now restart an application by clicking the Restart Server button from the information page of a project. Note that as of V19.02, this feature is in local Microclimate only.