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

September - 2023

PreviousOctober - 2023NextAugust - 2023

Last updated 9 months ago

The seasons have changed, and a lot more has changed with our product! This latest product update for Ozone – 1.2.16 focuses majorly on enhancing our experience by streamlining workflows, be it while adding providers, creating roles, or running and monitoring pipelines and deployments. While several minor fixes have gone into this release, below is a summary of what’s in store for this month. For context on the previous months, refer to our previous release notes .

Project Archival: The DevOps scenario in a typical global enterprise consists of multiple teams, infra, projects, tools, and microservices in the hundreds if not thousands. The common anchors holding all of these together are projects. The capability of archiving projects helps manage projects that can be temporary when external consultants and resources are involved or when there is a need to train or A/B test a couple of scenarios internally within an organization without fiddling with existing projects. This gives the ability to efficiently import, export, modify, and do more things with them as per changes in business requirements.

Jenkins Support: Users can now trigger external Jenkins jobs within the Ozone UI. Ozone ships with task and pipeline templates, we now have them available for this use case. Just look for the “Jenkins” keyword in the pipeline templates post, which you could either configure on the Ozone pipeline studio or clone and modify based on your needs.

Dynamic Role Creation: New roles can be created in the same workflow as inviting new members into the project. The invites are delivered by mail with a referral code to track rewards and audits. Within this process, if a role needs to be created while sending an invite, it can be done with just a single click. Just select the permission levels across 25+ resources, name the role with a description, and hit on invite. While the new user gets an email to the project, the role, too, gets saved in RBAC for future uses.

Pipeline and Release Navigation: As and how a project matures, the number of pipelines and releases increase. However, not in monstrous volumes as it is in platforms that do not use reusable pipelines. To help find the right pipelines and releases, users can simply search them by their names and run or manage them from the results.

Enhanced Validation for Provider Creation: Ozone supports multitudes of providers, and their creation flows are a crucial part of the user experience. To streamline this, we have validation of all field types (emails, tokes, etc.) to prevent issues from arising at the end of the provider addition process.

Licencing Updates: Ozone service providers have the control to seamlessly edit and update license plans for their end customers on the go, giving more flexibility and control of their Ozone subscribers.

Logs for Backups: While backups are a key part of cluster management, in case of success or failure, logs are now provided for more detailed alerts and troubleshooting.

Contextual Errors: There’s a lot that can be done on Ozone and hence, there are instances where many errors may pop up. This could be either while adding new providers, attaching a cluster, or running a pipeline. In this release, more context and dynamicity has been added to the error notifications to make users aware of what exactly the ambiguity is which then quickens troubleshooting.

here