We’re bringing you the latest Ozone release – 1.2.11, which has a host of major fixes and enhancements. We had a suite of new UI flows and capabilities that were introduced in our last release, which you can refer to here.
Here’s a summary of the specifics for this release:
Flexibility for quick and custom onboarding onto Ozone: New users are taken to a quick onboarding flow once they log in to Ozone. The quick flow provides a bootstrapped repository, a hello-world application, and a trial cluster that is live for a limited time frame. This helps new users get accustomed to the UI of Ozone and allows you to deploy the application through the quickstart flow in under 7 minutes. However, suppose you wish to use your own repositories and microservices and attach your own cluster. In that case, you can just toggle to the custom flow and follow the instructions on linking the resources.
While this feature has been there for quite some time, the UI for the custom and quick-start toggle has been further streamlined.
Improved context for notifications: Providers like cloud, SCM, container registries, SSOs, APMs, cloud storage, etc., can be synced and integrated with Ozone under the “Providers” menu. In this release, every time a specific resource gets successfully synced with the platform, users receive notifications with details on the synced resources and CTAs within them to perform contextual actions on these resources.
Attach your own cluster in QuickStart if the trial cluster is not created: As stated above in the QuickStart flow, a trial cluster is provided to new users, which will be live for a limited time. However, as this involves setting up an infrastructure, even if it is a basic cluster, chances are that the process may not be completed. In such an unlikely scenario, users now have the option to attach their own cluster during the QuickStart flow and get on ahead with running the bootstrapped pipeline to deploy the hello-world application without any further hiccups.
Enhanced cluster configuration: While attaching your cluster, once Ozone and its agents get installed on it, the screen automatically updates to display the configuration screen to enable the features you want on that cluster and the environment you want to associate it with.
Post cluster creation, in the clusters list-view screen, you can navigate to cluster analytics which shows the cluster health along with insights across namespaces, nodes, configurations, networks, storage, and more. You can edit cluster configurations on this screen as well, which helps streamline the process of cluster management.
Other minor fixes:
In the pipeline and release run view, the UI has been further improved to clearly show the connections between the tasks and pipelines to give a better visualization of their components.
For screens that have a list view, there’s a new implementation of the lazy-loading feature to optimize performance
Fixed the cluster status inconsistency during cluster creation
Fixed the latency for third-party SSO logins
The virtual trial clusters are now made non-editable, considering they are proprietary to Ozone
Ozone is focused on eliminating every complexity of a DevOps team. It simplifies and automates containerized and decentralised application deployments across hybrid cloud and diverse blockchain networks. Ozone integrates seamlessly with major tools across CI, CD, analytics and automation to support your software delivery end to end for even the most complex scenarios.