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

November - 2023

PreviousFebruary - 2024NextOctober - 2023

Last updated 9 months ago

We hope you guys had a wonderful Thanksgiving! We are eternally grateful to our employees, teams, and customers who have contributed to evolving Ozone over the years to where we stand now with their efforts and insights!

Over the previous month, we have been busy with a few more feature additions and enhancements for the 1.2.18 release of Ozone. Here’s a summary:

  1. Deployment Verification: Ozone integrates across monitoring tool stacks to ingest data like events, logs, metrics, and APM (Application Performance Monitoring) to identify and flag anomalies and later automate rollbacks in case the pre-defined threshold is breached. In this release, we have optimized the dashboard to provide more real-time insights into irregularities while allowing for a custom threshold setup post in which a rollback or an alert has to be triggered.

  1. Native Integration for Triggering External CI Pipelines: In the new release, Ozone natively integrates with Jenkins. With our task catalog and the Ozone pipeline studio, this means that external pipelines from Jenkins can be triggered within Ozone in a low-code/no-code approach. In ArgoCD-derived solutions, this is typically achieved by an incoming webhook. With our native support for Jenkins pipelines, you can trigger them and observe logs from within Ozone. This makes it useful for large-scale organizations, which typically take time to migrate to a next-generation CI/CD solution.

  2. Ozone-AI for Pipeline Conversions and Migrations: As you may already know, Ozone leverages the Tekton framework to provide reusable task and pipeline templates for enterprises. Being the world’s first platform to make Tekton accessible, the team has taken a step further in making migrations to Tekton more streamlined with the Ozone AI engine. There are two main use cases under this:

Automating pipeline conversions to Tekton with LLM: This new feature of Ozone automates the conversion of existing Jenkins pipelines into reusable Tekton pipelines within minutes, making migrations to Tekton a piece of cake. It leverages large language models (LLMs) which are fine-tuned using proprietary and open-source data to optimize these legacy to Tekton pipeline conversions. As of this release, support is for Jenkins pipeline conversions and later, this will be extended to GitLab and Azure DevOps pipelines.

Intelligent Prompt-driven Tekton Pipeline Generation: This feature of Ozone AI gives a whole new meaning to “low-code/no-code” DevOps. As the name suggests, users can simply ask the AI engine to “create a pipeline that deploys XYZ workload to the attached AKS cluster,” and they will instantly be presented with a Tekton YAML for the pipeline. Users can then save the pipeline or customize it if needed on the Ozone Pipeline Studio - A drag-and-drop pipeline configurator, and run the pipeline. By inputting just their use cases in simple English, Ozone enables smart reusable pipeline generation on the go, enabling teams to re-focus on what matters, while the platform does what it does best: automating CI/CD end-to-end with intelligence.

Enhancements:

  • Cluster attach: Once a cluster is attached, the cluster status sync has been optimized along with other scenarios where clusters are a dependency.

  • Standardized in-app messages: In order to provide better context on the errors and their causes, the in-app toaster messages have been tweaked for better message delivery.

!

Click here for a detailed demo of Ozone AI in action