We use Mission Control for cloud-native developments where the underlying layer is Kubernetes. We do deployments, and we check the code in GitHub and integrate with GitLab. In GitLab, we have the Git Actions, and it triggers the CI/CD pipeline.
It's all based on the underlying cloud-native development perspective and the actual deployment in the cloud. It depends on the particular flow from the development environment to the staging environment and the cloud deployment. That's why it's in a hybrid cloud, and we have two deployment topologies. One is vm cloud, and the other is vCloud on AWS.
AWS is the public cloud part of it. We also have the Azure Cloud, and Azure is our hybrid cloud environment. This is basically for the use cases around the CI/CD and monitoring the CI/CD cloud-native deployments in the azure cloud. If we have containerized images that have to be deployed in azure cloud, we monitor them using the Tanzu Mission Control.