OpenShift Administration Interview Questions and Answers [2025]

Cluster Management

1. What is OpenShift cluster architecture?

• Consists of master and worker nodes.
• Masters manage API and etcd.
• Workers run application pods.
• Uses Kubernetes for orchestration.
• Ensures secure networking via CNI.
• Supports high availability.

This architecture ensures scalability for interviews.

2. Why use OpenShift for cluster management?

OpenShift simplifies Kubernetes management with integrated tools like the web console, Operators, and automated upgrades. It offers RBAC and SCC for security. Compared to vanilla Kubernetes, it reduces complexity for admins. Validate cluster setup in a sandbox to demonstrate expertise for certification interviews.

3. When do you add worker nodes to a cluster?

• Add nodes for workload scaling.
• Use oc adm manage-node to add.
• Configure node labels for scheduling.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure cluster capacity.

Workloads exceed capacity. This shows scaling skills.

4. Where do you configure cluster settings?

Configure cluster settings via the OpenShift Web Console or oc edit clusteroperators. Adjust configurations like node selectors or API settings. Validate in a sandbox environment to ensure stability. Monitor with Prometheus to demonstrate cluster management skills for interviews.

5. Who manages cluster access?

• Cluster admin assigns RBAC roles.
• Use oc adm policy add-cluster-role-to-user.
• Restrict access to projects.
• Validate in sandbox environment.
• Monitor with audit logs.
• Ensure least privilege.

This role showcases security expertise for interviews.

6. Which tools automate cluster provisioning?

OpenShift integrates with Ansible for node setup, Terraform for infrastructure, and IPI for automated installs. Use oc adm to manage nodes.

• Configure Ansible playbooks for nodes.
• Use Terraform for cloud setups.
• Validate in sandbox.
• Monitor with Prometheus.

This enhances automation for certification.

7. How do you troubleshoot cluster node issues?

• Check node status with oc get nodes.
• Inspect logs with oc adm node-logs.
• Verify network connectivity.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Use diagnostic scripts.

A node is NotReady. This shows troubleshooting skills.

8. What is the Cluster Operator in OpenShift?

Cluster Operators manage core components like etcd, API server, and networking. They ensure cluster health and upgrades. Check status with oc get clusteroperators. Validate in a sandbox to demonstrate cluster management skills for interviews.

9. Why perform cluster health checks?

• Ensure node and pod availability.
• Check with oc get clusteroperators.
• Monitor resource usage with Prometheus.
• Validate in sandbox environment.
• Prevent downtime risks.
• Support cluster stability.

Cluster performance degrades. This ensures reliability.

10. When do you scale cluster nodes?

Scale nodes when workloads increase or nodes fail. Use oc adm manage-node to add nodes or MachineSets for dynamic scaling. Validate in a sandbox environment to ensure capacity. Monitor with Prometheus to show scaling skills for interviews.

11. Where do you store cluster configurations?

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

Configs need recovery. This supports cluster management.

12. Who resolves cluster resource issues?

Nodes run out of CPU. The cluster admin adjusts MachineSets or node limits with oc adm manage-node. Monitor with Prometheus.

• Validate in sandbox environment.
• Check resource allocation.
• Ensure cluster stability.
• Monitor node performance.

This shows resource management for interviews.

13. Which metrics monitor cluster health?

• Track node CPU/memory in Prometheus.
• Monitor pod restart rates.
• Analyze network with CNI metrics.
• Validate in sandbox environment.
• Monitor with Grafana.
• Automate alerts.

This demonstrates observability skills.

14. How do you handle node failures?

A node is unreachable. Check status with oc get nodes. Drain with oc adm drain and replace via MachineSets. Validate in a sandbox to show cluster recovery skills for interviews.

15. What is the role of etcd in OpenShift?

• Stores cluster state and configs.
• Back up with oc adm backup etcd.
• Ensure high availability with replicas.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Support cluster reliability.

Data loss risks exist. This supports interviews.

16. Why secure cluster configurations?

Configs risk exposure. Use Secrets for sensitive data and RBAC for access control. Apply with oc create secret generic. Restrict via RBAC. Validate in a sandbox to show security skills for interviews.

17. How do you optimize cluster performance?

• Adjust node sizes with MachineSets.
• Optimize pod scheduling with taints.
• Monitor with Prometheus.
• Validate in sandbox environment.
• Ensure network efficiency.
• Scale resources dynamically.

Cluster runs slowly. This shows optimization skills.

18. Which strategies prevent cluster failures?

Cluster risks downtime. Use high availability for masters and regular etcd backups. Monitor with Prometheus for trends.

• Configure HA for masters.
• Validate in sandbox environment.
• Monitor failure patterns.
• Ensure network stability.

This ensures reliable clusters for interviews.

Security and RBAC

19. What are Security Context Constraints (SCC)?

• Define pod security policies.
• Restrict privileged containers.
• Configure with oc create scc my-scc.
• Enforce non-root users.
• Validate in sandbox.
• Monitor with audit logs.

SCCs enhance security for interviews.

20. Why use RBAC in OpenShift?

RBAC controls user access to resources, ensuring least privilege. Configure roles with oc adm policy add-role-to-user. Compared to manual access, it simplifies management. Validate in a sandbox to show security skills for certification interviews.

21. When do you configure SCC for pods?

• Use for sensitive workloads.
• Apply with oc create scc my-scc.
• Restrict privileged access.
• Validate in sandbox environment.
• Monitor with audit logs.
• Ensure compliance.

Pods need security. This shows security expertise.

22. Where do you manage RBAC roles?

Manage RBAC in the OpenShift Web Console or with oc adm policy add-cluster-role-to-user. Assign roles like cluster-admin or edit. Validate in a sandbox to prevent unauthorized access. Monitor with audit logs to show security skills for interviews.

23. Who assigns cluster roles?

• Cluster admin assigns roles.
• Use oc adm policy add-cluster-role-to-user.
• Restrict to least privilege.
• Validate in sandbox environment.
• Monitor with audit logs.
• Collaborate with teams.

Access needs control. This shows security expertise.

24. Which tools enhance cluster security?

Cluster faces threats. Use SCC for pod restrictions and RBAC for access control. Integrate with network policies.

• Configure SCC with oc create.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Automate security checks.

This shows security expertise for interviews.

25. How do you troubleshoot SCC issues?

• Check pod events with oc describe pod.
• Verify SCC with oc describe scc.
• Adjust SCC permissions.
• Validate in sandbox environment.
• Monitor with audit logs.
• Use diagnostic scripts.

Pods fail due to SCC. This shows troubleshooting skills.

26. What causes RBAC permission errors?

Users lack access. Check role bindings with oc describe rolebinding. Assign correct roles with oc adm policy add-role-to-user. Validate in sandbox to show security skills for interviews.

27. Why do pods run as privileged?

• Misconfigured SCC allows privileged access.
• Check with oc describe scc.
• Restrict with non-privileged SCC.
• Validate in sandbox environment.
• Monitor with audit logs.
• Ensure least privilege.

Security risks arise. This shows security expertise.

28. When do you rotate service account tokens?

Rotate tokens after breaches or expirations using oc create sa new-token. Update DeploymentConfig to use new tokens. Validate in a sandbox to ensure secure access. Monitor with audit logs to show security skills for interviews.

29. Where do you audit RBAC policies?

• Use oc describe rolebinding for roles.
• Check audit logs in EFK stack.
• Restrict access via RBAC.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure compliance.

Unauthorized access occurs. This shows security expertise.

30. Who resolves SCC violations?

Pods violate SCC. The cluster admin adjusts SCC with oc edit scc restricted. Monitor with audit logs.

• Validate in sandbox environment.
• Check pod configurations.
• Ensure security compliance.
• Monitor violations.

This shows security troubleshooting for interviews.

31. Which metrics track security events?

• Monitor audit logs in Prometheus.
• Track unauthorized access attempts.
• Analyze with EFK stack.
• Validate in sandbox environment.
• Monitor with Grafana.
• Automate alerts.

Security needs visibility. This shows observability skills.

32. How do you secure cluster APIs?

APIs are exposed. Enable RBAC and configure HTTPS for the API server. Validate in a sandbox to show security skills for interviews.

33. What causes pod security failures?

• Misconfigured SCC or pod YAML.
• Check with oc describe pod.
• Apply restricted SCC.
• Validate in sandbox environment.
• Monitor with audit logs.
• Fix pod configurations.

Pods violate policies. This shows troubleshooting skills.

34. Why use OAuth for cluster access?

OAuth integrates with identity providers for secure user authentication. Configure via oc adm policy add-cluster-role-to-user. Validate in a sandbox to ensure secure access. Monitor with audit logs to show security expertise for interviews.

35. When do you configure project quotas?

• Use to limit project resources.
• Configure with oc create quota my-quota.
• Restrict CPU/memory usage.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure resource fairness.

Projects overuse resources. This shows resource management.

Networking

36. What is OpenShift’s networking model?

• Uses OVN-Kubernetes or SDN CNI.
• Supports pod-to-pod communication.
• Configures routes for external access.
• Enforces network policies.
• Validates in sandbox.
• Monitors with Prometheus.

This ensures robust networking for interviews.

37. Why use network policies?

• Restrict pod-to-pod traffic.
• Configure with oc apply -f policy.yaml.
• Enhance cluster security.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure compliance.

Pods need isolation. This shows networking expertise.

38. When do you configure routes?

Configure routes for external service access using oc expose svc/my-service. Validate in a sandbox to ensure accessibility. Monitor with Prometheus to show networking skills for interviews.

39. Where do you manage network configurations?

• Use oc edit network.operator.openshift.io.
• Configure in OpenShift Web Console.
• Adjust CNI or network policies.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure network stability.

Network needs setup. This shows networking expertise.

40. Who manages network policies?

The cluster admin configures network policies with oc apply -f policy.yaml, ensuring pod isolation. Validate in a sandbox and monitor with Prometheus to show networking skills for interviews.

41. Which tools troubleshoot network issues?

• Use oc describe pod for connectivity errors.
• Run ping or curl for tests.
• Analyze with networking tools like tcpdump.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Automate diagnostics.

Pods cannot communicate. This shows troubleshooting skills.

42. How do you secure cluster networking?

Network is exposed. Configure network policies and enable TLS for routes. Apply with oc apply -f policy.yaml.

• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure firewall alignment.
• Restrict external access.

This shows secure networking for interviews.

43. What causes network latency in clusters?

• Misconfigured CNI or network policies.
• Check with oc describe network.
• Optimize pod placement.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Use diagnostic tools.

Apps experience delays. This shows troubleshooting skills.

44. Why does a route fail to connect?

A route is inaccessible. Check configuration with oc describe route/my-route. Verify service selector and backend health. Validate in a sandbox to show networking skills for interviews.

45. When do you use ingress controllers?

• Use for advanced routing needs.
• Configure via Ingress Operator.
• Support path-based routing.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure external access.

Routes need customization. This shows networking expertise.

46. Where do you monitor network traffic?

Use Prometheus to monitor network metrics via the Cluster Network Operator. Analyze with Grafana dashboards. Validate in sandbox to show networking skills for interviews.

47. Who resolves network policy conflicts?

• Cluster admin fixes conflicts.
• Check with oc describe networkpolicy.
• Update with oc apply -f policy.yaml.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Minimize policy overlap.

Policies block traffic. This shows networking expertise.

48. Which steps secure a route?

A route exposes data. Configure TLS with oc create route edge --cert my-cert.pem. Apply network policies.

• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure certificate validity.
• Check route access.

This shows secure networking for interviews.

49. How do you handle network performance issues?

• Check Prometheus for latency metrics.
• Optimize CNI configurations.
• Adjust pod placement.
• Validate in sandbox environment.
• Monitor with Grafana.
• Scale network resources.

Network is slow. This shows performance expertise.

50. What causes pod network isolation?

Pods cannot communicate. Check network policies with oc describe networkpolicy. Adjust rules to allow traffic. Validate in a sandbox and monitor with Prometheus to show networking skills for interviews.

51. Why use OpenShift SDN?

• Provides pod-to-pod connectivity.
• Configure via Network Operator.
• Supports network policies.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure network scalability.

Cluster needs networking. This shows networking expertise.

52. When do you configure load balancers?

Use load balancers for high-traffic routes, configured via the Ingress Operator. Validate in a sandbox. Monitor with Prometheus to show load balancing skills for interviews.

Storage Management

53. What is a Persistent Volume (PV)?

• Provides storage for stateful apps.
• Configure via storage classes.
• Binds to PVCs for pods.
• Apply with oc apply -f pv.yaml.
• Validates in sandbox environment.
• Monitors with Prometheus.

PVs ensure data persistence for interviews.

54. Why does a PVC fail to bind?

A PVC cannot bind. Check storage class and PV availability with oc describe pvc/my-pvc. Ensure sufficient capacity. Validate in a sandbox to show storage skills for interviews.

55. When do you use dynamic provisioning?

• Use for automatic PV creation.
• Configure storage class in YAML.
• Apply with oc apply -f storageclass.yaml.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure storage scalability.

Storage needs automation. This shows storage expertise.

56. Where do you configure storage classes?

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

57. Who manages storage configurations?

• Cluster admin configures PVs/PVCs.
• Collaborate with developers for needs.
• Apply with oc apply -f pv.yaml.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure data persistence.

Apps need storage. This shows storage expertise.

58. Which storage backends support OpenShift?

Stateful apps need storage. Use Ceph RBD or NFS with storage classes. Configure via oc apply -f storageclass.yaml. Validate in a sandbox to show storage skills for interviews.

59. How do you troubleshoot storage issues?

• Check oc describe pvc/my-pvc for errors.
• Verify storage class and PV availability.
• Inspect pod events with oc describe pod.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Use diagnostic scripts.

Pods cannot mount storage. This shows troubleshooting skills.

60. What causes storage performance issues?

Storage is slow. Check IOPS with oc describe pvc/my-pvc. Upgrade storage class for better performance. Validate in a sandbox and monitor with Prometheus to show storage skills for interviews.

61. Why use volume snapshots?

• Create backups for stateful apps.
• Configure via snapshot YAML.
• Apply with oc apply -f snapshot.yaml.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure data recovery.

Data needs backups. This shows storage expertise.

62. When do you expand PVs?

Expand PVs when storage runs low, using oc edit pvc/my-pvc to increase capacity. Validate in a sandbox to show storage management skills for interviews.

63. Where do you store volume snapshots?

• Store in storage backend like Ceph.
• Configure via storage class.
• Apply with oc apply -f snapshot.yaml.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure snapshot availability.

Backups need storage. This shows storage skills.

64. Who resolves PV binding issues?

The cluster admin debugs with oc describe pvc/my-pvc and ensures PV availability. Validate in a sandbox. Monitor with Prometheus to show storage troubleshooting skills for interviews.

65. Which tools manage storage provisioning?

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

Storage needs management. This shows storage expertise.

66. How do you automate storage provisioning?

Storage needs automation. Use storage classes and integrate with cloud providers like AWS EBS.

• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure storage scalability.
• Apply with oc apply.

This shows automation skills for interviews.

67. What causes PV reclaim issues?

• Incorrect reclaim policy in PV.
• Check with oc describe pv/my-pv.
• Update policy to Delete/Retain.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Fix PVC bindings.

PVs cannot be reused. This shows troubleshooting skills.

68. Why does a pod fail to mount storage?

A pod cannot access PV. The PVC is misconfigured or PV is unavailable. Verify with oc describe pvc/my-pvc. Configure correct storage class. Validate in a sandbox to show storage skills for interviews.

69. When do you use StatefulSets for storage?

• Use for stateful apps like databases.
• Configure with oc apply -f statefulset.yaml.
• Ensure stable PV bindings.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Support data persistence.

Databases need storage. This shows application expertise.

Monitoring and Logging

70. What is the Cluster Monitoring Operator?

• Manages Prometheus and Grafana.
• Monitors cluster and app metrics.
• Configure via OpenShift Web Console.
• Validate in sandbox environment.
• Monitor with Grafana dashboards.
• Ensure observability.

This enhances monitoring for interviews.

71. Why does Prometheus miss metrics?

• Misconfigured service monitors.
• Check with oc describe servicemonitor.
• Verify pod annotations.
• Validate in sandbox.
• Monitor with Grafana.
• Fix metric collection.

Metrics are unavailable. This shows troubleshooting skills.

72. When do you configure monitoring alerts?

• Create alerts for CPU/memory issues.
• Configure in Prometheus with oc apply.
• Use PagerDuty for notifications.
• Validate in sandbox environment.
• Monitor with Grafana.
• Automate alert rules.

Outages need alerts. This shows monitoring expertise.

73. Where do you store monitoring data?

• Store metrics in Prometheus.
• Export logs to EFK stack.
• Configure via Cluster Logging Operator.
• Validate in sandbox environment.
• Monitor with Grafana.
• Ensure data retention.

Historical data is needed. This shows data management skills.

74. Who configures monitoring dashboards?

• Cluster admin creates Grafana dashboards.
• Configure via Cluster Monitoring Operator.
• Include CPU/memory metrics.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Share with teams.

Visibility is needed. This shows monitoring expertise.

75. Which tools enhance cluster observability?

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

Cluster needs observability. This shows monitoring expertise.

76. How do you handle missing logs?

Logs are unavailable. Check EFK stack configuration with oc describe clusterlogging. Configure log forwarding. Validate in sandbox.

• Monitor with Prometheus.
• Ensure log reliability.
• Fix logging configurations.

This shows logging expertise for interviews.

77. What causes high latency in monitoring?

• Overloaded Prometheus or EFK stack.
• Check with oc describe pod.
• Scale monitoring components.
• Validate in sandbox environment.
• Monitor with Grafana.
• Optimize configurations.

Monitoring is slow. This shows troubleshooting skills.

78. Why use the EFK stack for logging?

• Centralizes pod and cluster logs.
• Configure via Cluster Logging Operator.
• Visualize with Kibana dashboards.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure log visibility.

Logs need analysis. This shows logging expertise.

79. When do you use log-based metrics?

• Use to track errors or events.
• Configure in Prometheus with oc apply.
• Integrate with EFK stack.
• Validate in sandbox environment.
• Monitor with Grafana.
• Automate alerts.

Errors need tracking. This shows observability skills.

80. Where do you analyze cluster performance?

• Use Prometheus for cluster metrics.
• Visualize with Grafana dashboards.
• Check with oc adm top nodes.
• Validate in sandbox environment.
• Monitor with alerts.
• Ensure performance visibility.

Cluster needs optimization. This shows monitoring expertise.

81. Who resolves monitoring failures?

• Cluster admin debugs Prometheus/EFK.
• Check with oc describe pod.
• Fix configurations with oc apply.
• Validate in sandbox.
• Monitor with Grafana.
• Ensure observability.

Monitoring fails. This shows troubleshooting expertise.

82. Which steps optimize monitoring performance?

• Scale Prometheus/EFK pods.
• Optimize metric retention policies.
• Configure efficient service monitors.
• Validate in sandbox environment.
• Monitor with Grafana.
• Reduce metric overhead.

Monitoring is slow. This shows optimization skills.

83. How do you configure cluster alerts?

Alerts are needed. Configure Prometheus rules with oc apply -f alert.yaml. Integrate with PagerDuty. Validate in a sandbox to show monitoring skills for interviews.

84. What causes false monitoring alerts?

• Incorrect thresholds in Prometheus rules.
• Check with oc describe prometheusrule.
• Adjust alert conditions.
• Validate in sandbox environment.
• Monitor with Grafana.
• Optimize alert rules.

Alerts trigger unnecessarily. This shows troubleshooting skills.

85. Why does EFK miss logs?

• Misconfigured Fluentd or Elasticsearch.
• Check with oc describe clusterlogging.
• Fix log forwarding settings.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure log collection.

Logs are missing. This shows logging expertise.

Upgrades and Maintenance

86. What is the OpenShift upgrade process?

• Upgrades managed by Cluster Version Operator.
• Run oc adm upgrade --to=version.
• Back up etcd before upgrades.
• Validate in sandbox.
• Monitor with Prometheus.
• Ensure app compatibility.

This ensures smooth upgrades for interviews.

87. Why do upgrades fail?

• Incompatible apps or resource issues.
• Check with oc get clusteroperators.
• Fix dependencies pre-upgrade.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure etcd backups.

Upgrade stalls. This shows troubleshooting skills.

88. When do you schedule cluster maintenance?

Schedule maintenance during low-traffic periods. Use oc adm drain for node maintenance. Validate in a sandbox to minimize downtime. Monitor with Prometheus to show maintenance skills for interviews.

89. Where do you check upgrade status?

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

Upgrade status is unclear. This shows monitoring expertise.

90. Who performs cluster upgrades?

• Cluster admin initiates upgrades.
• Use oc adm upgrade --to=version.
• Collaborate with developers for compatibility.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure minimal downtime.

Cluster needs updating. This shows administrative expertise.

91. Which steps prepare for upgrades?

• Back up etcd with oc adm backup.
• Check app compatibility.
• Test in sandbox environment.
• Validate with oc get clusteroperators.
• Monitor with Prometheus.
• Plan rollback strategies.

Upgrade risks downtime. This shows preparation skills.

92. How do you handle upgrade failures?

An upgrade fails. Check logs with oc get clusteroperators. Roll back with oc adm upgrade --to=previous-version. Validate in a sandbox to show recovery skills for interviews.

93. What causes etcd backup failures?

• Insufficient storage or permissions.
• Check with oc adm backup etcd.
• Fix storage or RBAC issues.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure backup integrity.

Backups fail. This shows troubleshooting skills.

94. Why perform regular maintenance?

• Prevent performance degradation.
• Patch nodes with oc adm drain.
• Monitor with Prometheus dashboards.
• Validate in sandbox environment.
• Ensure cluster stability.
• Support compliance.

Cluster needs upkeep. This shows maintenance expertise.

95. When do you drain nodes?

Drain nodes during maintenance or upgrades using oc adm drain node-name. Validate in a sandbox to ensure minimal disruption. Monitor with Prometheus to show maintenance skills for interviews.

96. Where do you store etcd backups?

• Store in external storage like S3.
• Back up with oc adm backup etcd.
• Ensure secure access via RBAC.
• Validate in sandbox.
• Monitor with Prometheus.
• Ensure backup availability.

Backups need storage. This shows backup expertise.

97. Who resolves upgrade compatibility issues?

• Cluster admin checks compatibility.
• Review with oc get clusteroperators.
• Collaborate with developers for fixes.
• Validate in sandbox environment.
• Monitor with Prometheus.
• Ensure app stability.

Apps break post-upgrade. This shows troubleshooting expertise.

98. Which steps minimize upgrade downtime?

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

99. How do you automate cluster maintenance?

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

Maintenance needs automation. This shows automation expertise.

100. What causes node maintenance failures?

Node drain fails. Check pod eviction with oc describe node. Adjust pod disruption budgets. Validate in a sandbox and monitor with Prometheus to show maintenance skills for interviews.

101. Why use Operators for maintenance?

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

Components need automation. This shows Operator expertise.

102. When do you back up etcd?

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

103. Where do you monitor upgrade progress?

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

Upgrade progress is unclear. This shows monitoring expertise.