Reconciliation loop: observe desired state → compare actual state → act to close the gap → requeue on error
CRD design: use status subresource; define conditions following the Kubernetes API convention
Controller idempotency: every reconcile must be safe to run multiple times with the same input
Webhook types: validating (reject invalid resources) vs mutating (set defaults) — order matters
0 / 30 completed
1 / 30
The interviewer asks: "Explain the reconciliation loop in a Kubernetes controller. What happens when a reconcile returns an error?" Which answer is most technically accurate?
Option B is the strongest. It describes the informer-backed cache (not direct API calls), the work queue with exponential backoff on error, the RequeueAfter pattern for polling, and the critical design requirement of idempotency. It also notes that the controller must assume other writers exist — a common oversight for engineers new to operator development. Option A says "the loop stops" on error — wrong; the work queue retries. Option C describes a polling loop — incorrect; controllers are event-driven. Option D marks the resource as Failed and stops — this would leave the resource in a broken state indefinitely.
2 / 30
The interviewer asks: "How do you design a CRD (Custom Resource Definition) for a new operator? What conventions should you follow?" Which answer is most complete?
Option B is the strongest. It covers seven specific CRD conventions: spec/status separation, the status subresource (and why — preventing race conditions), the metav1.Condition convention for status conditions, printer columns, API versioning with conversion webhooks, and structural schema validation. This is the complete set of CRD design decisions a senior operator developer should know. Option A describes the minimum structure but none of the conventions. Option C is copying — fast but misses conventions that may not be in the chosen example. Option D designs status after implementation — this order leads to status fields that do not reflect what users actually need.
3 / 30
The interviewer asks: "What is the difference between a validating admission webhook and a mutating admission webhook, and when do you use each?" Which answer is most precise?
Option B is the strongest. It correctly states the ordering (mutating before validating), describes what each can do (mutating: modify; validating: accept/reject only), gives concrete use cases for each, explains the dependency benefit (validating can assume defaults are set), and addresses the critical operational question of fail-open vs fail-closed. Option A is a minimal description without ordering, use cases, or operational concerns. Option C is wrong about triggering conditions — both webhook types are triggered by write operations (CREATE, UPDATE, DELETE). Option D treats validating webhooks as redundant — wrong, because mutating webhooks cannot reject resources.
4 / 30
The interviewer asks: "How do you test a Kubernetes operator? What testing strategy do you use?" Which answer demonstrates the most layered approach?
Option B is strongest. It defines three testing layers (unit with fake client, integration with envtest, E2E with kind), names specific tools (controller-runtime fake client, envtest, kind), tests idempotency explicitly, covers leader election and external modification scenarios, and tests the negative path (missing references → meaningful status condition). Option A is manual testing only — not scalable or reproducible. Option C skips controller testing, which is the most complex and error-prone part. Option D uses Helm chart tests — validates installation but not operator behaviour.
5 / 30
The interviewer asks: "How do you handle operator upgrades without downtime for managed resources?" Which answer shows the most mature operational thinking?
Option C is the strongest. It addresses five specific upgrade concerns: leader election continuity, CRD backward compatibility (never remove fields, use conversion webhooks), reconcile safety for legacy resource states, staged rollout (canary per namespace), and status preservation. This is the complete operational picture. Option A deletes and recreates the operator — resource state and continuity are at risk. Option B uses OLM — valid for OLM-managed operators but does not explain the underlying mechanisms. Option D relies on RollingUpdate — handles pod replacement but does not address CRD compatibility or legacy resource state.
6 / 30
Review Comment: "This pod is constantly restarting! The logs show a 'Failed to create resource' error. Can you investigate the deployment configuration and ensure the necessary RBAC permissions are granted?" Which of the following actions would be MOST appropriate for your next step, as the operator developer?
This scenario tests understanding of common Kubernetes troubleshooting and operator responsibilities. The review comment points to a specific problem (resource creation failure), requiring focused investigation rather than generic monitoring or scaling. RBAC permissions are frequently the root cause of problems with new operators – confirming they're correctly set up is crucial.
7 / 30
Slack Message from a Team Lead: "Hey @john.doe, we've got a spike in errors related to our `MyCustomResource` objects failing to update. Can you quickly look into the operator's logic and see if there are any known issues or potential conflicts with other operators?
This question evaluates response to a real-world operational alert. The operator developer's primary role is troubleshooting issues within their controlled resources. The prompt requires a targeted investigation of the update logic for the relevant custom resource – it's not about broad infrastructure problems or immediate code reversion.
8 / 30
PR Description: "Implemented a new feature to automatically scale our `MyCustomResource` deployments based on CPU utilization. Added logic to monitor CPU usage and adjust the number of replicas accordingly. This should improve application performance and resource efficiency.
A good PR description should clearly communicate *what* was changed and *why*. This response focuses on functionality and benefits – it's a solid starting point. However, production operators need to consider operational aspects like error handling, rollback strategies, and monitoring during scaling events.
9 / 30
Stand-up Update: "I've been working on improving the operator's resilience to network outages. I implemented retry logic for failed API calls and added circuit breakers to prevent cascading failures.
Stand-up updates should be concise and focus on *what* was achieved and *why* it matters. This response correctly identifies proactive measures taken to improve operator stability – a core responsibility of an operator developer. The focus is on resilience and availability.
10 / 30
Scenario: Your operator manages a fleet of databases. A critical update to the underlying database engine requires a rolling upgrade – you need to ensure no data is lost and minimal downtime. Which approach would be MOST appropriate for achieving this, from an operator development perspective?
Rolling upgrades are fundamental to minimizing downtime in Kubernetes. This requires careful monitoring of each database instance during the upgrade process – a phased rollout allows for quick identification and resolution of any issues without disrupting the entire fleet. This demonstrates operational maturity.
11 / 30
Review Comment: "This pod is constantly restarting! The logs show a 'Failed to create resource' error. Can you investigate the deployment configuration and ensure the necessary RBAC permissions are granted?" Which of the following actions would be MOST appropriate for your next step, as the operator developer?
This scenario tests understanding of common Kubernetes troubleshooting and operator responsibilities. The review comment points to a specific problem (resource creation failure), requiring focused investigation rather than generic monitoring or scaling. RBAC permissions are frequently the root cause of problems with new operators – confirming they're correctly set up is crucial.
12 / 30
Slack Message from a Team Lead: "Hey @john.doe, we've got a spike in errors related to our `MyCustomResource` objects failing to update. Can you quickly look into the operator's logic and see if there are any known issues or potential conflicts with other operators?
This question evaluates response to a real-world operational alert. The operator developer's primary role is troubleshooting issues within their controlled resources. The prompt requires a targeted investigation of the update logic for the relevant custom resource – it's not about broad infrastructure problems or immediate code reversion.
13 / 30
PR Description: "Implemented a new feature to automatically scale our `MyCustomResource` deployments based on CPU utilization. Added logic to monitor CPU usage and adjust the number of replicas accordingly. This should improve application performance and resource efficiency.
A good PR description should clearly communicate *what* was changed and *why*. This response focuses on functionality and benefits – it's a solid starting point. However, production operators need to consider operational aspects like error handling, rollback strategies, and monitoring during scaling events.
14 / 30
Stand-up Update: "I've been working on improving the operator's resilience to network outages. I implemented retry logic for failed API calls and added circuit breakers to prevent cascading failures.
Stand-up updates should be concise and focus on *what* was achieved and *why* it matters. This response correctly identifies proactive measures taken to improve operator stability – a core responsibility of an operator developer. The focus is on resilience and availability.
15 / 30
Scenario: Your operator manages a fleet of databases. A critical update to the underlying database engine requires a rolling upgrade – you need to ensure no data is lost and minimal downtime. Which approach would be MOST appropriate for achieving this, from an operator development perspective?
Rolling upgrades are fundamental to minimizing downtime in Kubernetes. This requires careful monitoring of each database instance during the upgrade process – a phased rollout allows for quick identification and resolution of any issues without disrupting the entire fleet. This demonstrates operational maturity.
16 / 30
Review Comment: "This pod is constantly restarting! The logs show a 'Failed to create resource' error. Can you investigate the deployment configuration and ensure the necessary RBAC permissions are granted?" Which of the following actions would be MOST appropriate for your next step, as the operator developer?
This scenario tests understanding of common Kubernetes troubleshooting and operator responsibilities. The review comment points to a specific problem (resource creation failure), requiring focused investigation rather than generic monitoring or scaling. RBAC permissions are frequently the root cause of problems with new operators – confirming they're correctly set up is crucial.
17 / 30
Slack Message from a Team Lead: "Hey @john.doe, we've got a spike in errors related to our `MyCustomResource` objects failing to update. Can you quickly look into the operator's logic and see if there are any known issues or potential conflicts with other operators?
This question evaluates response to a real-world operational alert. The operator developer's primary role is troubleshooting issues within their controlled resources. The prompt requires a targeted investigation of the update logic for the relevant custom resource – it's not about broad infrastructure problems or immediate code reversion.
18 / 30
PR Description: "Implemented a new feature to automatically scale our `MyCustomResource` deployments based on CPU utilization. Added logic to monitor CPU usage and adjust the number of replicas accordingly. This should improve application performance and resource efficiency.
A good PR description should clearly communicate *what* was changed and *why*. This response focuses on functionality and benefits – it's a solid starting point. However, production operators need to consider operational aspects like error handling, rollback strategies, and monitoring during scaling events.
19 / 30
Stand-up Update: "I've been working on improving the operator's resilience to network outages. I implemented retry logic for failed API calls and added circuit breakers to prevent cascading failures.
Stand-up updates should be concise and focus on *what* was achieved and *why* it matters. This response correctly identifies proactive measures taken to improve operator stability – a core responsibility of an operator developer. The focus is on resilience and availability.
20 / 30
Scenario: Your operator manages a fleet of databases. A critical update to the underlying database engine requires a rolling upgrade – you need to ensure no data is lost and minimal downtime. Which approach would be MOST appropriate for achieving this, from an operator development perspective?
Rolling upgrades are fundamental to minimizing downtime in Kubernetes. This requires careful monitoring of each database instance during the upgrade process – a phased rollout allows for quick identification and resolution of any issues without disrupting the entire fleet. This demonstrates operational maturity.
21 / 30
Review Comment: "This pod is constantly restarting! The logs show a 'Failed to create resource' error. Can you investigate the deployment configuration and ensure the necessary RBAC permissions are granted?" Which of the following actions would be MOST appropriate for your next step, as the operator developer?
This scenario tests understanding of common Kubernetes troubleshooting and operator responsibilities. The review comment points to a specific problem (resource creation failure), requiring focused investigation rather than generic monitoring or scaling. RBAC permissions are frequently the root cause of problems with new operators – confirming they're correctly set up is crucial.
22 / 30
Slack Message from a Team Lead: "Hey @john.doe, we've got a spike in errors related to our `MyCustomResource` objects failing to update. Can you quickly look into the operator's logic and see if there are any known issues or potential conflicts with other operators?
This question evaluates response to a real-world operational alert. The operator developer's primary role is troubleshooting issues within their controlled resources. The prompt requires a targeted investigation of the update logic for the relevant custom resource – it's not about broad infrastructure problems or immediate code reversion.
23 / 30
PR Description: "Implemented a new feature to automatically scale our `MyCustomResource` deployments based on CPU utilization. Added logic to monitor CPU usage and adjust the number of replicas accordingly. This should improve application performance and resource efficiency.
A good PR description should clearly communicate *what* was changed and *why*. This response focuses on functionality and benefits – it's a solid starting point. However, production operators need to consider operational aspects like error handling, rollback strategies, and monitoring during scaling events.
24 / 30
Stand-up Update: "I've been working on improving the operator's resilience to network outages. I implemented retry logic for failed API calls and added circuit breakers to prevent cascading failures.
Stand-up updates should be concise and focus on *what* was achieved and *why* it matters. This response correctly identifies proactive measures taken to improve operator stability – a core responsibility of an operator developer. The focus is on resilience and availability.
25 / 30
Scenario: Your operator manages a fleet of databases. A critical update to the underlying database engine requires a rolling upgrade – you need to ensure no data is lost and minimal downtime. Which approach would be MOST appropriate for achieving this, from an operator development perspective?
Rolling upgrades are fundamental to minimizing downtime in Kubernetes. This requires careful monitoring of each database instance during the upgrade process – a phased rollout allows for quick identification and resolution of any issues without disrupting the entire fleet. This demonstrates operational maturity.
26 / 30
Review Comment: "This pod is constantly restarting! The logs show a 'Failed to create resource' error. Can you investigate the deployment configuration and ensure the necessary RBAC permissions are granted?" Which of the following actions would be MOST appropriate for your next step, as the operator developer?
This scenario tests understanding of common Kubernetes troubleshooting and operator responsibilities. The review comment points to a specific problem (resource creation failure), requiring focused investigation rather than generic monitoring or scaling. RBAC permissions are frequently the root cause of problems with new operators – confirming they're correctly set up is crucial.
27 / 30
Slack Message from a Team Lead: "Hey @john.doe, we've got a spike in errors related to our `MyCustomResource` objects failing to update. Can you quickly look into the operator's logic and see if there are any known issues or potential conflicts with other operators?
This question evaluates response to a real-world operational alert. The operator developer's primary role is troubleshooting issues within their controlled resources. The prompt requires a targeted investigation of the update logic for the relevant custom resource – it's not about broad infrastructure problems or immediate code reversion.
28 / 30
PR Description: "Implemented a new feature to automatically scale our `MyCustomResource` deployments based on CPU utilization. Added logic to monitor CPU usage and adjust the number of replicas accordingly. This should improve application performance and resource efficiency.
A good PR description should clearly communicate *what* was changed and *why*. This response focuses on functionality and benefits – it's a solid starting point. However, production operators need to consider operational aspects like error handling, rollback strategies, and monitoring during scaling events.
29 / 30
Stand-up Update: "I've been working on improving the operator's resilience to network outages. I implemented retry logic for failed API calls and added circuit breakers to prevent cascading failures.
Stand-up updates should be concise and focus on *what* was achieved and *why* it matters. This response correctly identifies proactive measures taken to improve operator stability – a core responsibility of an operator developer. The focus is on resilience and availability.
30 / 30
Scenario: Your operator manages a fleet of databases. A critical update to the underlying database engine requires a rolling upgrade – you need to ensure no data is lost and minimal downtime. Which approach would be MOST appropriate for achieving this, from an operator development perspective?
Rolling upgrades are fundamental to minimizing downtime in Kubernetes. This requires careful monitoring of each database instance during the upgrade process – a phased rollout allows for quick identification and resolution of any issues without disrupting the entire fleet. This demonstrates operational maturity.
What does "Kubernetes Operator Developer Interview Questions — Best-Answer Practice" cover?
Practice answering Kubernetes Operator Developer interview questions in professional English. 5 exercises on CRDs, controllers, reconciliation loops, operator SDK, and admission webhooks.
How many questions are in this interview set?
This set has 30 exercises, each with a full explanation.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do these exercises include model answers?
Yes. Each interview question gives you several possible responses and asks you to pick the one that communicates most clearly and completely — the explanation then breaks down exactly why that answer works, including the specific vocabulary a strong candidate would use.
What if I choose an answer that isn't the strongest one?
You'll see which option was correct and read a full explanation of why it's stronger than the alternatives, plus the key vocabulary and phrasing worth reusing in a real interview.
Can I retry the questions?
Yes — use the "Try again" button on the results screen to reset and go through the set again.
Is this the same as a real technical or behavioural interview?
No — it's focused practice for the language side of interviewing: recognising which phrasing sounds precise and confident versus vague, and knowing the vocabulary interviewers expect for this role. It won't replace mock interviews, but it builds the vocabulary you'll need in one.
Where can I find interview prep for other roles?
Browse the full Interview exercises hub for 170+ modules covering behavioural, technical, and system design rounds across dozens of IT roles, or check the "Next up" link below to continue.
Do I need an account, and is my progress saved?
No account is needed. Progress is tracked only for your current visit — reloading or leaving the page resets the counter.
Who writes these interview questions?
Every question is written by the CoderSlingo team based on real technical interview patterns for this role, then reviewed for accuracy and clarity.