Kubernetes
Quick answer
On Kubernetes, run IdentityIQ as a Deployment with ConfigMaps and Secrets, an external database, and services for UI and task nodes.
Key takeaways
- Prerequisites for Kubernetes
- Step-by-step install path
- Common pitfalls and fixes
- Verification after install
Running IdentityIQ on Kubernetes adds orchestration, self-healing and horizontal scaling on top of the containerised deployment. The application runs as a Deployment of pods, configuration lives in ConfigMaps and Secrets, and the database stays external and managed. Kubernetes is powerful here but only pays off once the containerisation fundamentals are solid.
Prerequisites
- A built, registry-hosted IdentityIQ container image.
- A Kubernetes cluster and access to deploy.
- An external managed database reachable from the cluster.
Step by step
- 1. Push the image to a registry the cluster can pull from.
- 2. Define a Deployment and a Service for the IdentityIQ pods.
- 3. Store configuration in ConfigMaps and credentials in Secrets, mounted or injected as environment variables.
- 4. Point at the external database via the Secret/ConfigMap connection settings.
- 5. Add readiness and liveness probes so Kubernetes only routes traffic to healthy pods and restarts unhealthy ones.
- 6. Scale deliberately: separate UI-serving pods from task/background pods, since they have different resource profiles.
Verify
Confirm pods reach ready state, probes pass, the Service exposes the UI, and the app connects to the database. Test that killing a pod results in a clean, automatic replacement.
Kubernetes notes
- Keep the database out of the cluster, use a managed database service.
- Use Secrets for credentials, never plain ConfigMaps or image layers.
- Separate UI and task workloads so batch jobs do not starve interactive pods.
- Plan how background/task processing is coordinated across replicas.
Common pitfalls
- Running the database in-cluster without proper persistence.
- Secrets stored insecurely as ConfigMaps.
- No probes, so traffic hits pods that are not ready.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
What are the prerequisites for Kubernetes?
- A. The application and app-server logs, which usually point to database, Java or permission issues.
- B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- C. Confirm the app server starts, the schema is present, and login works.
Show answer
B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
How do you verify the install?
- A. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- B. Confirm the app server starts, the schema is present, and login works.
- C. The application and app-server logs, which usually point to database, Java or permission issues.
Show answer
B. Confirm the app server starts, the schema is present, and login works.
Confirm the app server starts, the schema is present, and login works.
Where do you look first on failure?
- A. Confirm the app server starts, the schema is present, and login works.
- B. The application and app-server logs, which usually point to database, Java or permission issues.
- C. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
Show answer
B. The application and app-server logs, which usually point to database, Java or permission issues.
The application and app-server logs, which usually point to database, Java or permission issues.