Top OpenShift FAQs Asked in Interviews [2025]

Application Deployment

1. What is a DeploymentConfig in OpenShift?

• Manages application deployments and updates.
• 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 building container images from source code, reducing manual effort compared to Docker builds. It uses builder images to compile code and supports triggers for automated deployments. Configure with oc new-app --source my-repo.git to streamline app deployment processes.

3. When do you use oc new-app?

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

Quick app deployment is needed to simplify workflows.

4. Where do you configure app environment variables?

Configure environment variables in DeploymentConfig using oc set env dc/my-app KEY=VALUE for non-sensitive data. Store sensitive data in Secrets with oc create secret generic. Validate configurations in a test project to ensure proper application behavior and settings.

5. Who manages application deployments?

• Developers initiate app deployments.
• Admins configure cluster policies.
• Use oc apply -f dc.yaml for setup.
• Validate in test project.
• Monitor with Prometheus.
• Ensure collaborative workflows.

Teams manage deployments to maintain app stability.

6. Which tools support OpenShift deployments?

OpenShift supports multiple tools for streamlined deployments. Use Ansible for automation, Jenkins for CI/CD integration, and Helm for packaged deployments. Validate tool configurations in a test project. Monitor deployment success with Prometheus to ensure reliability.

7. How do you roll back a deployment?

• Use oc rollback dc/my-app for rollback.
• Check logs with oc logs dc/my-app.
• Verify previous configuration in YAML.
• Validate in test project.
• Monitor with Prometheus.
• Ensure stable recovery.

Failed deployments require rollback to restore functionality.

8. What is an image stream?

An image stream manages container image versions, enabling automatic updates and triggering deployments. Create with oc create imagestream my-app and link to DeploymentConfigs. Validate in a test project to ensure image management and deployment automation.

9. Why use templates for deployments?

• Standardize app configurations across teams.
• Store templates in OpenShift Catalog.
• Apply with oc apply -f template.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Simplify deployment workflows.

Templates ensure consistency in application setups.

10. When do you use ConfigMaps?

ConfigMaps store non-sensitive configuration data for applications, applied with oc create configmap my-config --from-file=config.properties. They decouple configuration from container images. Validate in a test project to ensure proper app behavior and configuration management.

11. Where do you store sensitive data?

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

Sensitive data requires secure management for apps.

12. Who troubleshoots deployment failures?

Developers debug application issues using oc logs dc/my-app, while admins address cluster-level problems. Collaboration ensures quick resolution of deployment failures. Validate fixes in a test project and monitor with Prometheus to maintain stability.

13. Which resources define an app?

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

Apps require multiple resources for functionality.

14. How do you scale an application?

Scale applications manually with oc scale dc/my-app --replicas=3 or dynamically using HorizontalPodAutoscaler with oc autoscale dc/my-app. Validate scaling in a test project to ensure performance under load and monitor with Prometheus.

15. What is the OpenShift web console?

• Provides UI for managing apps.
• Visualizes deployment and resource status.
• Supports Route and Service creation.
• Validate in test project.
• Monitor with dashboards.
• Simplifies developer tasks.

The console enhances app management efficiency.

16. Why secure app deployments?

Deployments risk exposing sensitive data, requiring secure practices. Use Secrets for credentials and RBAC for access control. Validate in a test project to ensure security. Monitor with audit logs to prevent unauthorized access.

17. How do you configure health checks?

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

Health checks maintain application uptime and stability.

18. Which strategies ensure zero-downtime deployments?

Rolling deployments prevent downtime by gradually updating pods. Configure maxSurge and maxUnavailable in DeploymentConfig YAML to control pod transitions.

• Apply with oc apply -f dc.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure seamless updates.

Zero-downtime deployments are critical for production apps.

CI/CD Pipelines

19. What is a BuildConfig?

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

BuildConfigs automate image creation for CI/CD.

20. Why use Tekton for pipelines?

Tekton provides Kubernetes-native CI/CD pipelines with reusable tasks, offering better integration than Jenkins for OpenShift. Configure pipelines with oc apply -f pipeline.yaml to automate builds and deployments efficiently.

21. When do you configure build triggers?

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

Triggers automate builds for code changes.

22. Where do you store build artifacts?

Store build artifacts in OpenShift’s internal registry using oc tag my-image:latest for accessibility. External registries can be used for broader sharing. Validate in a test project to ensure availability. Monitor with Prometheus to track artifact usage.

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 collaboration.

Pipelines require coordinated management for efficiency.

24. Which tools enhance CI/CD pipelines?

Tekton enables Kubernetes-native pipelines, while Jenkins supports legacy CI/CD workflows. Integrate with Git for source control.

• Configure with oc apply -f pipeline.yaml.
• Validate in test project.
• Monitor with Prometheus.
• Ensure build reliability.

Tools improve pipeline automation and scalability.

25. How do you troubleshoot build failures?

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

Build failures require systematic debugging to resolve.

26. What causes build timeouts?

Builds timeout due to resource constraints or slow dependencies. Increase timeout settings in BuildConfig with oc edit bc/my-build. Validate in test project and monitor with Prometheus to ensure timely builds.

27. Why do builds fail repository access?

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

Builds cannot fetch code, requiring authentication fixes.

28. When do you use Docker builds?

Docker builds are used when S2I is insufficient for custom requirements. Define a Dockerfile in the repository and configure BuildConfig with oc edit bc/my-build. Validate in a test project to ensure image creation. Monitor with Prometheus to confirm build success.

29. Where do you debug pipeline failures?

• Check logs with oc logs pipeline/my-pipeline.
• Inspect TaskRun events with oc describe taskrun.
• Verify BuildConfig triggers.
• Validate in test project.
• Monitor with Prometheus.
• Use diagnostic tools.

Pipelines fail, requiring detailed debugging.

30. Who resolves pipeline issues?

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

• Validate in test project.
• Monitor with Prometheus.
• Check TaskRun configurations.
• Ensure pipeline stability.

Pipeline issues disrupt CI/CD workflows.

31. Which metrics monitor pipeline performance?

• Track build success rates in Prometheus.
• Monitor build duration metrics.
• Analyze with scripts.
• Validate in test project.
• Monitor pipeline efficiency.
• Set performance alerts.

Metrics ensure pipeline reliability and optimization.

32. How do you automate pipeline triggers?

Automate triggers in BuildConfig with oc set triggers bc/my-build --from-git for Git commits. Integrate with webhooks for real-time updates. Validate in a test project to ensure automated pipeline execution.

33. What causes pipeline resource exhaustion?

• High CPU or memory in builds.
• Check with oc describe bc/my-build.
• Adjust limits in BuildConfig YAML.
• Validate in test project.
• Monitor with Prometheus.
• Optimize resource usage.

Pipelines overload clusters, requiring resource tuning.

34. Why use Jenkins in OpenShift?

Jenkins supports legacy CI/CD workflows and integrates with OpenShift via templates. Deploy with oc new-app jenkins-ephemeral for pipeline automation. Validate in a test project to ensure compatibility. Monitor with Prometheus to maintain pipeline performance.

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

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

External tools enhance pipeline flexibility.

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.
• Validate in test project.
• Monitor with Prometheus.

Routes enable external access for applications.

37. Why configure network policies?

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

Network policies secure application traffic.

38. When do you use secure Routes?

Secure Routes are used for encrypted traffic. Configure edge termination with oc create route edge --cert my-cert.pem. Validate in a test project to ensure secure access and monitor with Prometheus.

39. Where do you manage Route configurations?

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

Routes require precise configuration management.

40. Who configures network access?

Admins configure network access using RBAC with oc adm policy add-role-to-user view user1 -n my-project. Validate in a test project to ensure secure access. Monitor with Prometheus to maintain network integrity.

41. Which tools troubleshoot Route issues?

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

Route issues require effective troubleshooting tools.

42. How do you secure a Route?

Secure Routes with TLS using oc create route edge --cert my-cert.pem for encryption. Validate in a test project.

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

Secure Routes protect application traffic.

43. What causes Route timeouts?

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

Route timeouts disrupt user access.

44. Why does a service lack external access?

Services lack external access due to missing Routes. Create with oc expose svc/my-service and verify service selectors. Validate in a test project to restore external connectivity.

45. When do you use path-based routing?

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

Path-based routing supports multiple apps.

46. Where do you monitor Route traffic?

Monitor Route traffic in Prometheus via Cluster Monitoring Operator and visualize with Grafana dashboards. Validate in test project to ensure traffic observability. Check route performance metrics for optimization.

47. Who resolves Route configuration errors?

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

Route errors require admin intervention.

48. Which steps secure Routes with RBAC?

Secure Routes by restricting access with RBAC using oc adm policy add-role-to-user view user1 -n my-project. Validate in a test project.

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

RBAC ensures secure Route management.

49. How do you optimize Route performance?

• Monitor latency with Prometheus.
• Adjust timeout in route YAML.
• Scale backend pods with oc scale.
• Validate in test project.
• Monitor with Grafana.
• Optimize service settings.

Route performance impacts user experience.

50. What causes Route failures?

Route failures occur due to incorrect service selectors or backend pod issues. Check with oc describe route/my-route and validate in a test project to ensure connectivity and monitor with Prometheus.

51. Why use OVN-Kubernetes in OpenShift?

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

OVN-Kubernetes enhances network performance.

52. When do you configure load balancing?

Configure load balancing for high-traffic Routes using round-robin in route YAML. Validate in a test project to ensure even traffic distribution. Monitor with Prometheus to maintain performance.

Storage

53. What is a Persistent Volume Claim?

• Requests storage for applications.
• Defines size and access modes.
• Binds to Persistent Volumes.
• Apply with oc apply -f pvc.yaml.
• Validate in test project.
• Monitor with Prometheus.

PVCs ensure data persistence for apps.

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

Pods fail to mount PVCs due to incorrect storage class or access mode settings. Verify with oc describe pvc/my-pvc and update YAML. Validate in a test project to restore storage access.

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.

Dynamic provisioning simplifies storage management.

56. Where do you configure storage classes?

Define storage classes in YAML with oc apply -f storageclass.yaml for dynamic provisioning. Validate in test project to ensure proper storage allocation. Monitor with Prometheus for availability.

57. Who manages PVC configurations?

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

PVCs require coordinated management.

58. Which storage types support stateful apps?

Stateful apps use block storage like Ceph RBD or NFS, configured via storage classes. Validate in a test project to ensure data persistence. Monitor with Prometheus to confirm storage reliability.

59. How do you troubleshoot storage issues?

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

Storage issues disrupt app functionality.

60. What causes PVC binding failures?

PVCs fail to bind due to unavailable Persistent Volumes or incorrect storage class settings. Check with oc describe pvc/my-pvc and validate in a test project to ensure binding success.

• Monitor with Prometheus.
• Ensure PV availability.
• Update storage class.
• Verify binding events.

Binding failures prevent storage access.

61. Why use volume snapshots?

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

Snapshots protect against data loss.

62. When do you expand PVCs?

Expand PVCs when storage capacity is insufficient using oc edit pvc/my-pvc to increase size. Validate in a test project to ensure apps have adequate storage and monitor with Prometheus.

63. Where do you store volume snapshots?

• Store in CSI-compatible storage backend.
• Configure with oc apply -f snapshot.yaml.
• Ensure secure storage access.
• Validate in test project.
• Monitor with Prometheus.
• Verify snapshot integrity.

Snapshots ensure data recovery and availability.

64. Who resolves PVC mounting issues?

Admins debug PVC mounting issues with oc describe pvc/my-pvc and ensure PV availability. Validate in a test project to restore storage access. Monitor with Prometheus to confirm resolution.

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.

Tools streamline storage management processes.

66. How do you automate storage provisioning?

Automate storage provisioning using storage classes with AWS EBS for dynamic allocation. Apply with oc apply -f storageclass.yaml.

• Validate in test project.
• Monitor with Prometheus.
• Ensure storage scalability.
• Verify provisioning success.

Automation enhances storage efficiency.

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.

Slow storage impacts application performance.

68. Why does a pod lose data?

Pods lose data due to missing PVCs or ephemeral storage usage. Configure PVC in DeploymentConfig with oc edit dc/my-app. Validate in a test project to ensure data persistence.

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.

Stateful apps require stable storage configurations.

Monitoring

70. What is Prometheus in OpenShift?

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

Prometheus provides critical monitoring capabilities.

71. Why do pods fail with CrashLoopBackOff?

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

CrashLoopBackOff indicates application issues.

72. When do you use oc debug?

Use oc debug pod/my-pod to access a pod’s shell for troubleshooting runtime issues. Validate in a test project to diagnose problems and monitor with Prometheus to ensure resolution.

73. Where do you view app logs?

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

Logs are essential for debugging apps.

74. Who debugs app failures?

Developers debug app failures with oc logs my-pod, while admins address cluster issues with oc describe pod. Collaboration ensures effective resolution. Validate in a test project and monitor with Prometheus for stability.

75. Which tools enhance monitoring?

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

Monitoring tools improve cluster visibility.

76. How do you handle high latency?

High latency requires checking Prometheus for metrics and scaling pods with oc scale dc/my-app. Optimize app code or resources. Validate in a test project.

• Monitor with Prometheus.
• Ensure performance stability.
• Optimize network settings.
• Verify scaling effectiveness.

Latency impacts application performance.

77. What causes missing logs?

• Misconfigured EFK stack settings.
• Check with oc describe clusterlogging.
• Configure Fluentd for log forwarding.
• Validate in test project.
• Monitor with Prometheus.
• Fix logging configurations.

Missing logs hinder debugging efforts.

78. Why use liveness probes?

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

Liveness probes maintain application health.

79. When do you use readiness probes?

Use readiness probes to ensure pods are ready to receive traffic, configured in DeploymentConfig YAML with oc apply -f dc.yaml. Validate in a test project to prevent downtime and monitor with Prometheus.

80. Where do you analyze performance metrics?

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

Metrics drive performance optimization.

81. Who monitors app alerts?

Admins configure Prometheus alerts via Cluster Monitoring Operator and integrate with PagerDuty for notifications. Validate in test project to ensure alert reliability. Monitor with Grafana for timely issue detection.

82. Which steps fix pod crashes?

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

Pod crashes require immediate resolution.

83. How do you implement zero-downtime deployments?

Implement zero-downtime deployments using Rolling strategy in DeploymentConfig with maxSurge and maxUnavailable settings. Validate in a test project to ensure seamless updates and monitor with Prometheus.

84. What causes high CPU usage?

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

High CPU usage impacts performance.

85. Why integrate Prometheus?

Prometheus integrates with OpenShift to collect and monitor cluster and app metrics, enabling proactive issue detection. Configure via Cluster Monitoring Operator and visualize with Grafana for comprehensive observability.

Cluster Management

86. What is OpenShift’s cluster architecture?

• Includes master and worker nodes.
• Masters manage API and etcd.
• Workers run application pods.
• Uses Kubernetes for orchestration.
• Validate in test cluster.
• Monitor with Prometheus.

Architecture ensures scalability and reliability.

87. Why perform cluster health checks?

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

Health checks maintain cluster performance.

88. When do you scale cluster nodes?

Scale nodes during high workloads using oc adm manage-node or MachineSets for additional capacity. Validate in a test cluster to ensure performance and monitor with Prometheus.

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.

Configurations ensure cluster recoverability.

90. Who resolves cluster issues?

Admins debug cluster issues with oc get nodes and collaborate with developers for pod-related problems. Validate in a test cluster to ensure resolution. Monitor with Prometheus to maintain stability.

91. Which tools automate cluster tasks?

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

Automation tools enhance cluster efficiency.

92. How do you handle node failures?

Handle node failures by draining with oc adm drain node-name and replacing via MachineSets. Validate in a test cluster to restore functionality and monitor with Prometheus for stability.

93. What causes etcd failures?

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

etcd failures disrupt cluster operations.

94. Why use Operators in cluster management?

Operators automate component management, upgrades, and scaling in OpenShift. Install via OperatorHub and configure with oc apply -f operator.yaml. Validate in a test cluster to ensure functionality. Monitor with Prometheus for reliability.

95. When do you back up etcd?

• Back up before upgrades or maintenance.
• Use oc adm backup etcd for backups.
• Store in secure external storage.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure data recovery.

etcd backups protect cluster data.

96. Where do you monitor cluster health?

Monitor cluster health in Prometheus via Cluster Monitoring Operator and visualize with Grafana dashboards. Validate in test cluster to ensure observability. Check cluster operator status for issues.

97. Who performs cluster upgrades?

• Admins initiate upgrades with oc adm upgrade.
• Collaborate with developers for compatibility.
• Check logs with oc get clusteroperators.
• Validate in test cluster.
• Monitor with Prometheus.
• Ensure minimal downtime.

Upgrades maintain cluster functionality.

98. Which steps minimize upgrade downtime?

Use rolling upgrades and pre-test in a staging cluster to minimize downtime. Monitor with oc get clusteroperators and validate in a test cluster.

• Ensure operator compatibility.
• Monitor with Prometheus.
• Validate upgrade success.
• Plan maintenance windows.

Downtime impacts cluster availability.

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.

Automation reduces maintenance overhead.

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.

Maintenance failures disrupt cluster operations.

101. Why perform cluster backups?

Cluster backups protect against data loss using oc adm backup etcd for etcd data. Store backups securely and validate in a test cluster to ensure recoverability and monitor with Prometheus.

102. When do you drain nodes?

Drain nodes during maintenance or upgrades with oc adm drain node-name to evict pods safely. Validate in a test cluster to minimize disruption and monitor with Prometheus.

103. Where do you check upgrade status?

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

Upgrade status ensures cluster reliability.