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

October - 2023

PreviousNovember - 2023NextSeptember - 2023

Last updated 9 months ago

We’re about to come to the end of 2023 and approach the holiday season, and with that, we also come to you with another set of updates worth noting!

As most of you may already know, Ozone ships with a catalog of 100+ Tekton tasks that are vetted by the open-source community. We are now adding specific tasks to this extensive catalog, which have made it to this release. There have also been minor UI enhancements to optimize workflows further. Here’s a summary of the latest 1.2.17 release from Ozone:

  1. Tekton task additions: The following tasks have now been added and made available to users:

    • Support for Postman-Newman CLI as tasks - Newman is a command-line collection runner for Postman, a popular API development and testing tool. The Newman cli task in Ozone allows you to run Postman collections for quality control on Ozone.

    • The task for Python pytest

    • Support for GitLab pipeline trigger from Ozone Catalog

    • Support for scaling node groups of an EKS cluster as a task

    • Support for deploying AWS Lambda functions as a task.

2. Enabling and disabling schedules for pipelines and releases: The feature allows users to control or manage schedules. Enabling a Schedule: When a user enables a schedule associated with a pipeline or release, it means that the predefined actions or tasks specified in that schedule will be executed as scheduled. For example, if a scan pipeline schedule is enabled, it will trigger a routine scan pipeline as planned.

Disabling a Schedule: When a user disables a schedule, it prevents the predefined actions from being automatically executed according to the schedule. Disabling a schedule can be useful in situations where temporary adjustments or interruptions are necessary. For instance, disabling a deployment schedule can temporarily stop deployment pipelines.

  1. Selective namespace logging per cluster: Users can select which namespaces to log, which helps optimize storage and network costs. For example, the system namespaces provided by the cloud are stable and have no contextual value to developers. However, namespaces that host containers to which developers deploy are typically the ones that DevOps teams would like to monitor for logs.

Enhancements:

  1. Trial expiry alerts: While Ozone offers a 30-day free trial of its enterprise plan, it shifts back to the free tier after 30 days. To facilitate a smooth transition to paid plans, contextual alerts are set up to remind active users of the impending downgrade.

  2. Service account tokens can be set to “not expire” to facilitate developer access to clusters and logs without much dependency.

3. While configuring a pipeline run, a default timeout value is provided (1 hour) to terminate pipeline runs in case of issues and preserve resource consumption. The default timeout is customizable.

Fixes:

  1. Onboarding timeout now is 20 minutes to align with virtual cluster creation. This is to eliminate errors that pop up when the trial cluster expires.

  2. As Ozone boasts of a unified dashboard for multi-cluster visibility, clicking on any cluster now leads to the overview page to make it quicker to gather insights.