Most Asked OpenShift Interview Questions [2025]

Application Deployment

1. What is OpenShift’s DeploymentConfig?

• Manages app deployments in OpenShift.
• Supports Rolling and Recreate strategies.
• Triggers updates via image changes.
• Apply with oc apply -f dc.yaml.
• Ensures secure networking.
• Monitors with Prometheus.

DeploymentConfigs streamline app management for interviews.

2. Why use Source-to-Image for deployments?

Source-to-Image (S2I) automates image creation from source code, simplifying deployments. It uses builder images for compilation. Compared to manual Docker builds, S2I reduces complexity. Validate with oc new-app in a test project to show deployment skills.

3. When do you use oc new-app?

• Deploy apps from Git repositories.
• Run oc new-app my-repo.git.
• Support Docker images.
• Validate in test project.
• Monitor with Prometheus.
• Ensure quick setup.

Rapid app deployment is needed, showing deployment expertise.

4. Where do you configure app environment variables?

Configure environment variables in DeploymentConfig using oc set env dc/my-app. Store sensitive data in Secrets. Validate in a test project to ensure correct settings. Monitor with oc describe dc/my-app to show configuration skills.

5. Who manages app deployments in OpenShift?

• Developers initiate deployments.
• Admins configure cluster settings.
• Use oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure team collaboration.

Apps need deployment management, showing teamwork skills.

6. Which tools support OpenShift deployments?

OpenShift integrates with Ansible for automation, Jenkins for CI/CD, and Helm for packaging. Use oc new-app for quick setups.

• Validate in test project.
• Monitor with Prometheus.
• Automate with pipelines.
• Ensure app scalability.

This shows deployment tool expertise.

7. How do you roll back a failed deployment?

• Use oc rollback dc/my-app.
• Check logs with oc logs dc/my-app.
• Validate in test project.
• Monitor with Prometheus.
• Ensure stable rollback.
• Fix deployment issues.

A deployment fails in production, showing rollback skills.

8. What is an image stream in OpenShift?

An image stream manages container images, tracking updates and triggering deployments. Configure with oc create imagestream my-app. Validate in a test project to show image management skills.

9. Why use templates for app deployments?

• Ensure consistent app configs.
• Store in OpenShift Catalog.
• Apply with oc apply -f template.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Simplify team workflows.

Templates standardize deployments, showing configuration expertise.

10. When do you use ConfigMaps for apps?

Use ConfigMaps for non-sensitive app settings, applied with oc create configmap my-config. Validate in a test project for correct configuration. Monitor with oc describe cm/my-config to show deployment skills.

11. Where do you store sensitive app data?

• Use Secrets for sensitive data.
• Apply with oc create secret generic.
• Restrict via RBAC.
• Validate in test project.
• Monitor with audit logs.
• Ensure secure access.

Apps need secure configs, showing security skills.

12. Who troubleshoots app deployment failures?

Developers debug with oc logs dc/my-app and collaborate with admins for cluster issues. Validate in a test project.

• Monitor with Prometheus.
• Check oc describe dc.
• Fix code or configs.
• Ensure app stability.

Apps fail in production, showing troubleshooting expertise.

13. Which resources define an app in OpenShift?

• DeploymentConfig for app updates.
• Service for internal networking.
• Route for external access.
• Validate in test project.
• Monitor with Prometheus.
• Use ConfigMaps for settings.

This demonstrates app resource expertise.

14. How do you scale an app in OpenShift?

Scale apps with oc scale dc/my-app --replicas=3. Configure HorizontalPodAutoscaler for dynamic scaling. Validate in a test project to show scaling skills.

15. What is the role of OpenShift’s web console?

• Provides UI for app management.
• Visualizes deployment status.
• Supports route and service creation.
• Validate in test project.
• Monitor with dashboards.
• Simplify developer tasks.

The console aids app management for interviews.

16. Why secure app deployments?

Deployments expose sensitive data. Use Secrets for credentials and RBAC for access control. Apply with oc create secret generic my-secret. Validate in a test project to show secure deployment skills with RBAC.

17. How do you configure health checks for apps?

• Define liveness/readiness probes.
• Configure in DeploymentConfig YAML.
• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure app reliability.

Apps need health checks, showing reliability expertise.

18. Which strategies ensure reliable deployments?

Deployments fail intermittently. Use Rolling strategy and health checks in DeploymentConfig. Validate with oc describe dc/my-app.

• Monitor with Prometheus.
• Ensure zero downtime.
• Check image streams.
• Validate in test project.

This shows reliable deployment skills.

CI/CD Pipelines

19. What is a BuildConfig in OpenShift?

• Defines build processes for CI/CD.
• Supports S2I and Docker builds.
• Uses triggers for automation.
• Validates in test project.
• Monitors with Prometheus.
• Integrates with Git.

BuildConfigs streamline CI/CD for interviews.

20. Why use Tekton for CI/CD pipelines?

Tekton provides Kubernetes-native pipelines, supporting reusable tasks and automation. Compared to Jenkins, it integrates seamlessly with OpenShift. Configure with oc apply -f pipeline.yaml to show CI/CD skills.

21. When do you configure build triggers?

• Set triggers for Git commits.
• Configure with oc set triggers bc/my-build.
• Support automated builds.
• Validate in test project.
• Monitor with Prometheus.
• Ensure pipeline efficiency.

Builds need automation, showing CI/CD expertise.

22. Where do you store build artifacts?

Store artifacts in OpenShift’s integrated registry using oc tag my-image. Push to external registries if needed. Validate in a test project for availability. Monitor with oc describe is/my-image to show CI/CD skills.

23. Who manages CI/CD pipelines?

• DevOps engineers design pipelines.
• Developers configure BuildConfigs.
• Use oc create pipeline for Tekton.
• Validate in test project.
• Monitor with Prometheus.
• Ensure team alignment.

Pipelines need management, showing collaboration skills.

24. Which tools enhance CI/CD pipelines?

Use Tekton for Kubernetes-native pipelines and Jenkins for legacy CI/CD. Integrate with Git for automation.

• Validate in test project.
• Monitor with Prometheus.
• Configure pipeline triggers.
• Ensure build reliability.

This shows CI/CD tool expertise.

25. How do you troubleshoot build failures?

• Check logs with oc logs bc/my-build.
• Verify BuildConfig settings.
• Inspect Git access.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic scripts.

Builds fail in production, showing troubleshooting skills.

26. What causes build timeouts in CI/CD?

Builds timeout due to resource limits. Increase timeout in BuildConfig with oc edit bc/my-build. Validate in test project and monitor with Prometheus to show CI/CD skills.

27. Why do builds fail repository access?

• Missing credentials in BuildConfig.
• Add secrets with oc create secret.
• Verify repository URL.
• Validate in test project.
• Monitor with Prometheus.
• Ensure network access.

Builds cannot fetch code, showing troubleshooting expertise.

28. When do you use Docker builds in CI/CD?

Use Docker builds for custom images when S2I is insufficient. Define Dockerfile in repository and configure BuildConfig. Validate in a test project for image creation. Monitor with oc describe bc/my-build to show CI/CD skills.

29. Where do you debug pipeline failures?

• Use oc logs pipeline/my-pipeline.
• Check BuildConfig triggers.
• Verify repository access.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic tools.

Pipelines fail in production, showing debugging skills.

30. Who resolves pipeline issues?

DevOps engineers debug with oc logs pipeline/my-pipeline and collaborate with developers for fixes. Monitor with Prometheus.

• Validate in test project.
• Check pipeline stages.
• Ensure resource availability.
• Monitor execution.

Pipelines stall, showing teamwork skills.

31. Which metrics monitor pipeline performance?

• Track build success in Prometheus.
• Monitor build duration.
• Analyze with scripts.
• Validate in test project.
• Monitor pipeline efficiency.
• Automate alerts.

Pipelines need observability, showing monitoring skills.

32. How do you automate pipeline triggers?

Configure triggers in BuildConfig with oc set triggers bc/my-build. Integrate with Git webhooks. Validate in a test project to show CI/CD automation skills.

33. What causes pipeline resource exhaustion?

• Insufficient CPU for builds.
• Increase limits in BuildConfig YAML.
• Check with oc describe bc/my-build.
• Validate in test project.
• Monitor with Prometheus.
• Optimize resources.

Builds fail due to resources, showing troubleshooting skills.

34. Why use Jenkins in OpenShift CI/CD?

Jenkins supports legacy CI/CD workflows. Deploy via OpenShift template with oc new-app jenkins. Validate in a test project for pipeline automation. Monitor with Prometheus to show CI/CD integration skills.

35. When do you integrate external CI/CD tools?

• Use for complex pipeline needs.
• Integrate Jenkins or GitLab CI.
• Configure with oc apply -f pipeline.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure tool compatibility.

Pipelines need external tools, showing integration skills.

Networking

36. What is a Route in OpenShift?

• Exposes services to external traffic.
• Uses HAProxy for load balancing.
• Configure with oc expose svc/my-service.
• Supports TLS termination.
• Validates in test project.
• Monitors with Prometheus.

Routes ensure external access for interviews.

37. Why configure network policies?

• Restrict pod-to-pod communication.
• Define in networkpolicy.yaml.
• Apply with oc apply -f policy.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Enhance app security.

Apps need secure networking, showing expertise.

38. When do you use secure Routes?

Configure secure Routes with TLS for encrypted traffic using oc create route edge. Validate in a test project to ensure secure access. Monitor with Prometheus to show networking skills.

39. Where do you manage Route configurations?

• Use oc edit route/my-route.
• Configure in OpenShift Web Console.
• Adjust TLS or path-based routing.
• Validate in test project.
• Monitor with Prometheus.
• Ensure route accessibility.

Routes need customization, showing networking expertise.

40. Who configures network access?

Admins configure RBAC for Routes with oc adm policy add-role-to-user. Validate in a test project and monitor with Prometheus to show networking security skills.

41. Which tools troubleshoot Route issues?

• Use oc describe route/my-route.
• Run curl for access tests.
• Analyze with networking tools like tcpdump.
• Validate in test project.
• Monitor with Prometheus.
• Automate diagnostics.

Routes are inaccessible, showing troubleshooting skills.

42. How do you secure a Route?

Routes need encryption. Configure edge termination with oc create route edge --cert my-cert.pem. Validate in a test project.

• Monitor with Prometheus.
• Ensure certificate validity.
• Check route accessibility.
• Update firewall rules.

This shows secure networking expertise.

43. What causes Route timeouts?

• Misconfigured timeout in route YAML.
• Check with oc describe route/my-route.
• Adjust timeout settings.
• Validate in test project.
• Monitor with Prometheus.
• Ensure service availability.

Users report timeouts, showing troubleshooting skills.

44. Why does a service lack external access?

A service is unreachable. The Route is missing or misconfigured. Create with oc expose svc/my-service. Verify service selector. Validate in a test project to show networking skills.

45. When do you use path-based routing?

• Use for apps sharing domains.
• Configure in route YAML with path.
• Apply with oc apply -f route.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure routing accuracy.

Apps share domains, showing routing expertise.

46. Where do you monitor Route traffic?

Monitor Route metrics in Prometheus via Cluster Monitoring Operator. Analyze with Grafana dashboards. Validate in test project to show networking skills.

47. Who resolves Route configuration errors?

• Admins fix Route settings.
• Check with oc describe route/my-route.
• Update YAML for corrections.
• Validate in test project.
• Monitor with Prometheus.
• Collaborate with developers.

Routes fail to route traffic, showing troubleshooting expertise.

48. Which steps secure Routes with RBAC?

Unauthorized Route access occurs. Configure RBAC with oc adm policy add-role-to-user view user1 -n my-project. Validate in a test project.

• Monitor with Prometheus.
• Ensure least privilege.
• Check audit logs.
• Validate access controls.

This shows security expertise.

49. How do you optimize Route performance?

• Check Prometheus for latency metrics.
• Adjust Route timeout settings.
• Optimize backend service.
• Validate in test project.
• Monitor with Grafana.
• Scale pods if needed.

Routes are slow, showing performance expertise.

50. What causes Route failures?

Routes are inaccessible. Check configuration with oc describe route/my-route. Verify service selector and backend health. Validate in a test project and monitor with Prometheus to show networking skills.

51. Why use OVN-Kubernetes in OpenShift?

• Provides scalable pod networking.
• Supports network policies.
• Configure via Network Operator.
• Validate in test project.
• Monitor with Prometheus.
• Ensure network scalability.

OVN-Kubernetes enhances networking, showing expertise.

52. When do you configure load balancing?

Use load balancing for high-traffic Routes, configured in route YAML with round-robin. Validate in a test project. Monitor with Prometheus to show load balancing skills.

Storage

53. What is a Persistent Volume Claim?

• Requests storage for apps.
• Defines size and access mode.
• Binds to Persistent Volumes.
• Apply with oc apply -f pvc.yaml.
• Validates in test project.
• Monitors with Prometheus.

PVCs ensure data persistence for interviews.

54. Why does a pod fail to mount a PVC?

Pods cannot access storage due to PVC misconfiguration. Check with oc describe pvc/my-pvc. Verify storage class. Validate in a test project to show storage skills.

55. When do you use dynamic provisioning?

• Use for automated PV creation.
• Configure storage class in PVC.
• Apply with oc apply -f pvc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure storage scalability.

Storage needs automation, showing storage expertise.

56. Where do you configure storage classes?

Define storage classes in YAML for provisioning. Apply with oc apply -f storageclass.yaml. Validate in test project to show storage management skills.

57. Who manages PVC configurations?

• Admins configure PVCs for apps.
• Collaborate with developers for needs.
• Apply with oc apply -f pvc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure data persistence.

Apps need storage, showing storage expertise.

58. Which storage types support stateful apps?

Stateful apps need block storage like Ceph RBD or NFS. Configure via storage class. Validate in a test project to show storage skills.

59. How do you troubleshoot storage issues?

• Check oc describe pvc/my-pvc.
• Verify storage class and PV.
• Inspect pod events with oc describe pod.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic scripts.

Pods cannot mount storage, showing troubleshooting skills.

60. What causes PVC binding failures?

PVC fails to bind due to unavailable PVs. Check with oc describe pvc/my-pvc. Ensure storage class capacity. Validate in a test project and monitor with Prometheus to show storage skills.

61. Why use volume snapshots?

• Create backups for app data.
• Configure via snapshot YAML.
• Apply with oc apply -f snapshot.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure data recovery.

Data needs backups, showing storage expertise.

62. When do you expand PVCs?

Expand PVCs when storage runs low using oc edit pvc/my-pvc to increase capacity. Validate in a test project to show storage management skills.

63. Where do you store volume snapshots?

• Store in storage backend.
• Configure via storage class.
• Apply with oc apply -f snapshot.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure snapshot availability.

Snapshots need storage, showing storage skills.

64. Who resolves PVC mounting issues?

Admins debug with oc describe pvc/my-pvc and ensure PV availability. Validate in a test project. Monitor with Prometheus to show storage troubleshooting skills.

65. Which tools manage storage provisioning?

• Use storage classes for provisioning.
• Configure with oc apply -f storageclass.yaml.
• Integrate with Ceph or NFS.
• Validate in test project.
• Monitor with Prometheus.
• Automate storage setup.

Storage needs management, showing expertise.

66. How do you automate storage provisioning?

Storage needs automation. Use storage classes with AWS EBS for dynamic provisioning.

• Validate in test project.
• Monitor with Prometheus.
• Ensure storage scalability.
• Apply with oc apply.

This shows automation skills.

67. What causes storage performance issues?

• Low IOPS in storage backend.
• Check with oc describe pvc/my-pvc.
• Upgrade storage class performance.
• Validate in test project.
• Monitor with Prometheus.
• Optimize volume settings.

Storage is slow, showing troubleshooting skills.

68. Why does a pod lose data?

Data disappears after pod restart due to missing PVC or ephemeral storage. Verify with oc describe pod/my-pod. Configure PVC in YAML. Validate in a test project to show storage skills.

69. When do you use StatefulSets?

• Use for stateful apps like databases.
• Configure with oc apply -f statefulset.yaml.
• Ensure stable pod identities.
• Validate in test project.
• Monitor with Prometheus.
• Support data persistence.

Databases need stable storage, showing expertise.

Monitoring

70. What is Prometheus in OpenShift?

• Monitors cluster and app metrics.
• Integrated via Cluster Monitoring Operator.
• Visualizes with Grafana dashboards.
• Validates in test project.
• Sets alerts for issues.
• Ensures observability.

Prometheus enhances monitoring for interviews.

71. Why do pods fail with CrashLoopBackOff?

• App errors cause pod failures.
• Check logs with oc logs my-pod.
• Verify container image settings.
• Validate in test project.
• Monitor with Prometheus.
• Fix code or config.

Pods keep crashing, showing debugging skills.

72. When do you use oc debug?

• Access pod shell for debugging.
• Run oc debug pod/my-pod.
• Diagnose runtime issues.
• Validate in test project.
• Monitor with Prometheus.
• Ensure quick resolution.

Pods fail unexpectedly, showing debugging expertise.

73. Where do you view app logs?

• Use oc logs my-pod for logs.
• Access via OpenShift Web Console.
• Integrate with EFK stack.
• Validate in test project.
• Monitor with Prometheus.
• Ensure log availability.

Logs are needed for debugging, showing logging expertise.

74. Who debugs app failures?

• Developers debug with oc logs.
• Collaborate with admins for issues.
• Use oc describe pod for events.
• Validate in test project.
• Monitor with Prometheus.
• Fix code or configs.

Apps fail in production, showing troubleshooting expertise.

75. Which tools enhance monitoring?

• Use Prometheus for metrics.
• Integrate Grafana for visualization.
• Configure EFK for logging.
• Validate in test project.
• Monitor with alerts.
• Automate metric collection.

Clusters need visibility, showing observability skills.

76. How do you handle high latency?

Apps are slow in production. Check Prometheus for latency metrics. Optimize code or scale pods with oc scale dc/my-app. Validate in a test project.

• Monitor with Prometheus.
• Ensure performance stability.
• Optimize network settings.

This shows performance troubleshooting.

77. What causes missing logs?

• Misconfigured EFK stack.
• Check with oc describe pod/my-pod.
• Configure log forwarding.
• Validate in test project.
• Monitor with Prometheus.
• Fix logging settings.

Logs are unavailable, showing logging skills.

78. Why use liveness probes?

• Ensure pods run correctly.
• Configure in DeploymentConfig YAML.
• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Prevent app failures.

Pods need health checks, showing reliability expertise.

79. When do you use readiness probes?

• Ensure pods are ready for traffic.
• Configure in DeploymentConfig YAML.
• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Prevent downtime.

Apps need readiness checks, showing reliability skills.

80. Where do you analyze performance metrics?

• Use Prometheus for metrics.
• Visualize with Grafana dashboards.
• Check with oc adm top pod.
• Validate in test project.
• Monitor with alerts.
• Ensure performance visibility.

Performance issues occur, showing observability skills.

81. Who monitors app alerts?

• Admins set Prometheus alerts.
• Configure via Cluster Monitoring Operator.
• Integrate with PagerDuty.
• Validate in test project.
• Monitor with Grafana.
• Ensure alert reliability.

Alerts indicate issues, showing monitoring expertise.

82. Which steps fix pod crashes?

• Check logs with oc logs my-pod.
• Verify resource limits.
• Fix app code or configs.
• Validate in test project.
• Monitor with Prometheus.
• Scale pods if needed.

Pods crash repeatedly, showing debugging skills.

83. How do you implement zero-downtime deployments?

Deployments cause outages. Use Rolling strategy in DeploymentConfig. Configure maxSurge and maxUnavailable. Validate in a test project to show deployment expertise.

84. What causes high CPU usage?

• Insufficient pod resource limits.
• Check with oc adm top pod.
• Adjust limits in DeploymentConfig.
• Validate in test project.
• Monitor with Prometheus.
• Optimize app code.

Pods consume excessive CPU, showing troubleshooting skills.

85. Why integrate Prometheus?

• Provides app and cluster metrics.
• Configure via Cluster Monitoring Operator.
• Visualize with Grafana dashboards.
• Validate in test project.
• Monitor with alerts.
• Enhance observability.

Metrics are needed, showing monitoring expertise.

Cluster Management

86. What is OpenShift’s cluster architecture?

• Consists of master and worker nodes.
• Masters manage API and etcd.
• Workers run pods.
• Uses Kubernetes for orchestration.
• Validates in test cluster.
• Monitors with Prometheus.

Architecture ensures scalability for interviews.

87. Why perform cluster health checks?

• Ensure node availability.
• Check with oc get clusteroperators.
• Monitor resources with Prometheus.
• Validate in test cluster.
• Prevent downtime.
• Support cluster stability.

Cluster performance degrades, showing reliability skills.

88. When do you scale cluster nodes?

Scale nodes during workload spikes using oc adm manage-node or MachineSets. Validate in a test cluster to ensure capacity. Monitor with Prometheus to show scaling skills.

89. Where do you store cluster configurations?

• Store in etcd for persistence.
• Back up with oc adm backup etcd.
• Access via oc commands.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure backup integrity.

Configs need recovery, showing management skills.

90. Who resolves cluster issues?

• Admins debug with oc get nodes.
• Collaborate with developers for fixes.
• Use oc adm node-logs for errors.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure stability.

Nodes fail, showing troubleshooting expertise.

91. Which tools automate cluster tasks?

• Use Ansible for node setup.
• Terraform for infrastructure automation.
• Configure with oc adm.
• Validate in test cluster.
• Monitor with Prometheus.
• Automate scaling.

Clusters need automation, showing expertise.

92. How do you handle node failures?

Nodes are unreachable. Check status with oc get nodes. Drain with oc adm drain and replace via MachineSets. Validate in a test cluster to show recovery skills.

93. What causes etcd failures?

• Storage or network issues.
• Check with oc adm inspect etcd.
• Restore from backups.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure etcd stability.

etcd fails, showing troubleshooting skills.

94. Why use Operators in cluster management?

• Automate component management.
• Configure via OperatorHub.
• Support upgrades and scaling.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure efficiency.

Components need automation, showing Operator expertise.

95. When do you back up etcd?

Back up etcd before upgrades or maintenance using oc adm backup etcd. Validate in a test cluster to ensure data recovery. Monitor with Prometheus to show backup skills.

96. Where do you monitor cluster health?

Use Prometheus for metrics via Cluster Monitoring Operator. Analyze with Grafana dashboards. Validate in test cluster to show monitoring skills.

97. Who performs cluster upgrades?

• Admins initiate upgrades.
• Use oc adm upgrade --to=version.
• Collaborate with developers for compatibility.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure minimal downtime.

Clusters need updating, showing administrative expertise.

98. Which steps minimize upgrade downtime?

Upgrades cause outages. Use rolling upgrades and pre-test in a test cluster. Monitor with oc get clusteroperators. Validate to show upgrade skills.

99. How do you automate cluster maintenance?

• Use Ansible for node patching.
• Schedule with oc adm drain.
• Integrate with Prometheus alerts.
• Validate in test cluster.
• Monitor with Grafana.
• Ensure minimal disruption.

Maintenance needs automation, showing expertise.

100. What causes node maintenance failures?

• Pod eviction issues during drain.
• Check with oc describe node.
• Adjust pod disruption budgets.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure node stability.

Node drain fails, showing maintenance skills.

101. Why perform cluster backups?

• Protect against data loss.
• Back up etcd with oc adm backup.
• Store in secure storage.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure data recovery.

Clusters risk data loss, showing backup expertise.

102. When do you drain nodes?

Drain nodes during maintenance or upgrades using oc adm drain node-name. Validate in a test cluster to minimize disruption. Monitor with Prometheus to show maintenance skills.

103. Where do you check upgrade status?

• Use oc get clusteroperators for progress.
• Check logs in OpenShift Web Console.
• Monitor with Prometheus dashboards.
• Validate in test cluster.
• Ensure upgrade completion.
• Track operator status.

Upgrade status is unclear, showing monitoring expertise.