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

April - 2023

We are back with a huge list of new features and usability enhancements for the Ozone platform! To make it easier for our readers, we’ve come out with combined release notes covering 2023 YTD, followed by periodic updates as and how we progress.

Here’s what we’ve been up to for most of this year:

  1. App-of-app releases, aka release management on Ozone

Having interacted with many teams across diverse industries, the most common challenge faced was managing complex application releases to end-users, especially when a major fix is in place or an app undergoes major updates. In such scenarios, multiple microservices must be rolled out simultaneously and successfully across specific user bases.

The release management feature on Ozone lets you connect multiple pipelines associated with numerous microservices that form part of the release by dragging and dropping them on a visual canvas called the Ozone Pipeline Studio. The release is then deployed similarly to deploying an application. The only major difference is that this application would be deploying multiple others, hence the term “app of apps.”

The low-code GUI allows for quick configuration and deployment of releases, regardless of their complexity.

2. Ozone Pipeline Studio

This studio consists of an infinitely scaling canvas built over the Tekton DAG (directed acyclic graphs) that lets you connect and run multiple tasks in sequence or parallel. This helps quickly configure even the most complex of pipelines in just a few minutes, thanks to the low-code GUI. Here’s some more info:

  • Ozone ships with a catalog of 100+ pre-defined task templates that is accessible right inside the pipeline studio. Drag, drop, and connect the required tasks directly onto the canvas and customize the YAML if needed right there.

  • Connect tasks in any order of execution visually with the provision to modify the YAML with just a simple toggle between the visual and YAML editor.

  • Map input parameters to your tasks from upstream nodes and save the pipeline. All in under a few minutes!

  • Starting from configuring releases that consist of pipelines or the latter that consist of tasks, dive deeper into step-level information for each and every task to gain granular under-the-hood visibility.

  • Real-time release and pipeline run status and logs are made easily accessible across tasks and steps inside them.

Enhancements to the product

  1. To make working with pipelines easier, they are now moved out of microservice definitions and can be accessed independently.

  2. Backups are now first-class citizens with their own management console on the UI

  3. The user experience has been enhanced, and major workflow improvements have been made in this release. Here’s a snapshot of some of the major UX overhauls:

    • An all-new onboarding flow specially designed to allow new users to pull and deploy a sample application with a bootstrapped cluster and pipeline in just a few minutes

    • Activities related to setting up providers, environments, variables, helm channels, repositories, and clusters can now be done from the “Resources” menu

    • Assigning a role and project/s to new members who are invited to join Ozone can now be done during the time of member onboarding

    • Bulk invites can be sent by uploading a CSV for SSO integrations

    • Unlike the previous workflow, prerequisites for setting up providers or other resources are now handled during their respective configurations.

PreviousMay - 2023NextSeptember - 2022

Last updated 9 months ago