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

Jan - 2022

We’re just in the 1st week of this year and the notes for the latest release – 1.1.3 is out! This time, we have focused on streamlining day-2 ops for our users along with the usual fixes and improvements based on our user feedback.

Rollbacks are key to ensuring the high availabilities of applications even in cases of failed deployments. The new version has streamlined how rollbacks are initiated, along with adding a new feature for archiving clusters. It also supports cluster heartbeat mechanisms to understand when a cluster is offline. Following this, Ozone now features periodic cluster backups and restores as well.

Apart from other general fixes and improvements, you can now use your GitHub and GitLab accounts and log in to Ozone. All the details on this new release are as below:

New feature updates and how they positively impact your day-2 ops:

1. Rollback Deployments: The Rollback Deployment option lets you rollback your application to the last successful deployment. This helps in quick and safe recovery from a failed deployment without drastically affecting application availability.

To perform a rollback you would need pipeline execution permissions which would be available for user roles from and above a pipeline executive.

In this new release, every application pipeline can have a rollback pipeline associated with it, should things go awry. All you have to do is initiate the rollback pipeline and let things come back to how they were before. Here’s how you do it:

  • From Ozone’s dashboard, navigate to ‘Pipelines and Tasks’

  • From the pipelines screen, select the GUI-editor (for configuring pipelines without code: drag and drop pre-defined tasks)

  • Once you enter a pipeline name in the GUI editor, select the relevant rollback pipeline from the dropdown list

  • Select a task from the in-built task templates to build your pipeline and click on save. All done!

2. Cluster heartbeat mechanism: Cluster heartbeats are signals sent by a cluster to communicate that it is online and available. Lack of a signal would inevitably mean that the cluster is down. In this new release of Ozone, the platform recognizes these signals which in turn gives you the insight to plan for cluster archival accordingly.

3. Cluster archival: Running instances on external cloud vendors is always tricky. For one, you never know when there could be outages or you may need to plan your deployments based on them being deleted externally by any cloud provider.

Ozone now identifies and archives your clusters if they aren’t available which typically happens when they are deleted by the cloud provider externally.

4. Backups and Restores: Day-2 ops can get complicated and lead to large overheads. You need a platform that can help you streamline these tasks rather than adding to them. Backups and restores are a key part to your everyday operations and this new release supports configuring of a periodic automated backup. You can then restore to any Kubernetes cluster later on.

Enhancements and Integrations for Enriched Usability:

1. Login with GitLab and GitHub for SaaS editions: Be it for a free trial or onboarding your team onto the platform, Ozone supports logins with your GitHub and GitLab accounts. All you need to do is to acknowledge the following access:

  • Read the authenticated user’s personal information

  • Grants read-only access to the authenticated user’s profile through the /user API endpoint, which includes username, public email, and full name. Also grants access to read-only API endpoints under /users.

  • Allows read-only access to the user’s personal information using OpenID Connect

  • Grants read-only access to the user’s profile data using OpenID Connect.

  • Allows read-only access to the repository

  • Grants read-only access to repositories on private projects using Git-over-HTTP or the Repository Files API.

  • Allows read-only access to the user’s primary email address using OpenID Connect

  • Grants read-only access to the user’s primary email address using OpenID Connect.

  • Access the authenticated user’s API

  • Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry.

2. New user onboarding flow: Since the user base is now growing to multiple first-time users, we have added an onboarding flow that guides users right from the dashboard. A guided tour helps users create or attach their clusters, integrate tools, configure pipelines, onboard applications, and deploy and monitor them on Ozone.

Watch this space for more product updates!

PreviousMar - 2022NextNov - 2021

Last updated 9 months ago