Deployment lifecycle status
Every Keycloak deployment managed by Cloud-IAM follows a fully automated lifecycle, designed to ensure stability, reliability, and seamless upgrade compatibility.
You can monitor both the status and availability of your deployment at any time through the Cloud-IAM Console or API.
Deployment Status
The deployment status reflects the current operational phase of your Keycloak environment.
It changes based on actions or jobs you initiate, such as deploying a custom extension or updating configurations. These actions may temporarily transition the status as the system safely processes and applies changes.
Important
A change in deployment status does not necessarily indicate any impact on the availability for end users.
How to see the status of specific deployment
To access the status of your deployment, follow these steps:
- Open Cloud-IAM console
- Select the Keycloak deployment you want to inspect
- Look at the top of the page or the Last Deployment Status field this will display the current deployment status
What are different deployments statuses
Each status reflects a specific phase in your deployment’s lifecycle:
✅ RUNNING — Fully Operational
The deployment is active and functioning normally.
All features are available, including theme customization, realm management, and user authentication. No issues are detected, and no actions are in progress.
🔄 STARTING — Rolling Upgrade in Progress
This status appears when a system or configuration change has triggered a rolling upgrade. Typical triggers include deploying a custom extension or updating environment variables, allow lists, etc.
During this phase, which typically takes 5 to 10 minutes, each Keycloak node is restarted one by one, ensuring zero downtime for end users. While the upgrade is in progress, the deployment is temporarily frozen from additional changes to ensure consistency. Once all nodes complete the upgrade, the deployment returns to RUNNING.
❌ ERROR — Upgrade Failure
This status indicates a failure occurred during the upgrade process. Common causes include misconfigured or broken custom extensions.
Even in an ERROR state, the Keycloak cluster is often partially available, typically only one node has failed.
From an end-user perspective, this issue is usually seamless.
To restore full functionality, please contact Cloud-IAM Support. Our team will help diagnose and resolve the issue quickly.
🏗️ CREATING — Deployment in Progress
This status appears when a new Keycloak deployment is being provisioned.
Cloud-IAM is setting up the environment, initializing the Keycloak cluster, and applying your chosen configuration. Depending on the deployment size, this phase typically takes a few minutes to complete. Once ready, the status changes to RUNNING.
🗑️ DELETING — Removal in Progress
This status indicates that the deployment is being decommissioned.
Cloud-IAM is securely removing all associated resources and data in accordance with compliance standards. Once deletion is complete, the deployment will no longer appear in your Cloud-IAM Console.
Deployment Availability
The deployment availability reflects the real-time uptime of your Keycloak instance.
It is continuously monitored through internal probes and health checks to ensure your environment remains accessible and responsive.
How to see the availability status of specific deployment
To access the availability status of your deployment, follow these steps:
- Open Cloud-IAM console
- Select the Keycloak deployment you want to inspect
- Look at the Availability field this will display the current deployment status
What are different availability statuses
Cloud-IAM continuously monitors the health of your Keycloak deployment using internal probes and health checks. For more information on how monitoring and probes operate, refer to the Monitoring and Incident Detection page.
🟢 UP — Healthy
The Keycloak deployment is fully available and responding correctly to monitoring probes and health checks. All services are operating normally.
🔴 DOWN — Unavailable
The Keycloak deployment is currently not accessible based on monitoring probes and health checks.
When a deployment enters a DOWN state, our on-call operations team is automatically alerted and begins working immediately to diagnose and resolve the incident, restoring normal service.
