Exit Process for AppZ SRE deployments

The following section explains the high-level steps involved if and when the customer transitions out of the Cloud Control AppZ platform. Our intention is that customers have as smooth a process as possible if they decide to move out of AppZ. The Kubernetes cluster will function without interruptions, as the AppZ-based management is being done from the sidelines. The following table explains the components and the steps involved:

1.Kubernetes Cluster

The Kubernetes cluster managed by AppZ will continue to function without interruptions after AppZ is removed. The manifest files and images, which were dynamically created to set up the cluster, will also be provided to the customer so that they can continue to manage it in the future.

2.Application Stacks

The application stack runtimes used by the customer in the cluster will also remain as-is in the cluster. Customers can, in the future, use the distributions (and fixes and patches) available from the respective sources to maintain them.

3.Observability

The observability runs within the cluster with the customer. The customer will be able to use public distributions of Prometheus and Grafana to view the dashboards.

4.CI/CD Pipeline.

AppZ provides a dynamic pipeline for deployments. This function will not be available once AppZ is removed. However, if the customer desires so, we are happy to set up a CI/CD pipeline of the customer’s choice in the customer environment at an addtional charge.

5.Git Repository

Customer repository will continue to function without changes once AppZ is unhooked from the same.