Tutorials
  • Welcome to Ozone
  • Quick Onboarding
    • Creating a New Project
    • Creating Environments
    • Adding a Registry
    • Adding a Repository
    • Attaching Clusters
    • Creating a Microservice
    • Using out-of-the-box Pipeline Templates
    • Creating a new pipeline on the Ozone Pipeline Studio
    • Configuring Triggers for Automated Deployments
    • Adding a CD Provider
      • Jenkins Pipeline
  • Documentation
    • Dashboard
      • Ozone Dashboard
      • Analyze Metrics & Logs for Kubernetes Clusters
    • CI/CD
      • Create Microservice
        • Link a Git Repo
        • Map a Registry
        • Map to Environments
        • Build Config (Specify where the Docker file exists)
      • Link Pipelines to your Microservice
        • Default Pipelines that are linked
        • What are Input Sets?
        • Execute a linked pipeline
      • Catalog
        • External Pipelines
          • Supported Integrations
          • How to Link an External CI Integration
          • Conversion Of external pipelines to Tekton Pipelines
        • Tasks
          • Create a Custom task
        • Releases (Templates and Runs)
          • What are releases composed of (Pipelines & Approvals)
          • Create a Release Template
          • Run a Release Template
        • Running Your First Pipeline
        • Pipelines (Templates & Runs)
          • Adding Nodes to Canvas
          • Configuring Rollbacks at Pipeline Template
          • Secret Injection + Secrets
          • Input-result mapping between tasks
        • Initiating Pipeline run
          • Manually
      • Triggers
        • Scheduling a pipeline and/or a release run
        • Triggering a pipeline and/or a release run
          • From Github events
          • From GitLab events
          • From Jira events
          • Custom Webhook
          • From Harbor events
          • From Azure DevOps events
          • From Bitbucket events
          • From Dockerhub events
      • Observe your Microservice
      • Verify Your Microservice With AI
    • Helm
      • Create a Helm Channel
      • Create a Helm Release
      • Edit a Helm Release
    • DevSecOps
      • Security Dashboard
      • Scans
      • Supported Integrations
      • Run Your First Security Pipeline
      • Shift Left Policy Management
        • Policies
    • Backups
      • Pre-requisites
      • How do I schedule a backup to create snapshots?
      • How to take snapshots and how do I know the status of backups?
      • How do I restore snapshots to clusters?
    • Setup
      • Manage Cluster
        • Public Cluster
        • Reattach Cluster
      • Setting up Environments
      • Manage Secret
      • Manage Repos
      • Manage Registries
      • Integrations
        • Managing Cloud Integrations
          • AWS
          • Azure
          • GCP
        • Managing Source Code Integrations
          • GitHub
          • GitLab
          • Bit bucket
          • Azure DevOps Repos
          • Git Repo
          • Bitbucket Datacenter
        • Managing Container Registry
          • Docker
          • GCR
          • Harbor
          • Quay
          • Azure ACR
          • Adhoc Registry
        • Managing Container Orchestration
          • AWS EKS
          • GKE
          • Azure AKS
        • Managing Issue Trackers
        • Managing Continuous Deployment
          • Argo CD
          • Azure DevOps
          • Ansible Tower
        • Managing SSO
        • Managing Private Catalogs
        • Managing Notifications
        • Managing Security
          • Snyk
          • Prisma Cloud
        • Managing APM
          • NewRelic
        • Managing Cloud Storage
          • Minio
          • AWS S3 Bucket
          • Google Cloud Storage
          • Azure Blob Storage
        • Managing Network Tunnels
        • Manage Testing
          • K6
        • Managing Secret Store
          • Azure Key Vault
          • Google Secret Manager
          • AWS Secrets Manager
          • Hashicorp Vault
    • Settings
      • Role Based Access Control
        • Create a new role
        • Clone an Existing Role
        • Apply a role to a member
      • Ozone Identity Management
      • Audit Trails
      • Private Cluster Management
      • SSO
        • Pre-Requisites
        • Azure AD
      • Projects
        • Create a new Project
        • Archive a Project
        • Import and remove resources into the project
        • Add Members to a Project
      • Setup Alerts and Notifications
  • Release Notes
    • August - 2024
    • July - 2024
    • June - 2024
    • April - 2024
    • February - 2024
    • November - 2023
    • October - 2023
    • September - 2023
    • August - 2023
    • July - 2023
    • June - 2023
    • May - 2023
    • April - 2023
    • September - 2022
    • August - 2022
    • July - 2022
    • May - 2022
    • April - 2022
    • Mar - 2022
    • Jan - 2022
    • Nov - 2021
  • FAQ
    • In House Applications
    • COTS Applications
    • Tasks
    • Pipelines
    • Releases
    • Projects
    • Members
    • Environments
    • Variables
    • Roles
  • Use Cases
    • For Platform Engineers
      • Standardized Application Delivery Workflows
      • Unified Observability and Alerting
      • On Demand Workload Recovery
    • For Software Developers
      • On Demand Delivery
      • Scalable and Re-usable Workflows
Powered by GitBook
On this page
  1. Release Notes

May - 2023

PreviousJune - 2023NextApril - 2023

Last updated 9 months ago

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’s a summary of the specifics for this release:

  1. 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 repositories and microservices and attach your 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:

  1. 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.

  2. For screens that have a list view, there’s a new implementation of the lazy-loading feature to optimize performance

  3. Fixed the cluster status inconsistency during cluster creation

  4. Fixed the latency for third-party SSO logins

  5. The virtual trial clusters are now made non-editable, considering they are proprietary to Ozone

here