--- title: How to Build Kubernetes Operators: A Handbook for Devs description: A comprehensive guide to building Kubernetes operators from scratch, covering the full lifecycle from concept to production. Explains the difference between... canonical: https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How to Build Kubernetes Operators: A Handbook for Devs | daily.dev og:description: A comprehensive guide to building Kubernetes operators from scratch, covering the full lifecycle from concept to production. Explains the difference between... og:url: https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks og:image: https://api.daily.dev/og/posts/9m9zoXQKS.png og:image:alt: How to Build Kubernetes Operators: A Handbook for Devs og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How to Build Kubernetes Operators: A Handbook for Devs **[freeCodeCamp](https://daily.dev/sources/freecodecamp)** · [@karan_6864](https://daily.dev/karan_6864) · 29 min read · 4 upvotes · 0 comments ## Summary A comprehensive guide to building Kubernetes operators from scratch, covering the full lifecycle from concept to production. Explains the difference between CRDs, controllers, and operators, then walks through building VMOperator — a controller that manages a VirtualMachine custom resource backed by a mock HTTP provider. Covers reconciliation loop design, idempotency, finalizers, predicates, owned resources, cross-resource reconciliation, RBAC, packaging with Docker, leader election, concurrency tuning, rate limiting, security hardening, and observability with Prometheus metrics. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I stop a Kubernetes controller from reconciling in an infinite loop after it updates a resource's status? Use a predicate that filters out status-only updates before they trigger a reconcile. Register builder.WithPredicates(predicate.GenerationChangedPredicate{}) in SetupWithManager, since the generation field only increments when spec changes, not status. This drops events where nothing but status moved, so the controller's own status writes stop retriggering itself, leaving only meaningful spec changes or explicit requeues to trigger reconciliation. _daily.dev surfaces practical fixes like this for developers debugging their own operator reconcile loops._ ### How can a Kubernetes operator avoid creating a duplicate external resource if it crashes right after creating it but before writing the status? The gap happens because the external create call succeeds and returns an id, but the process crashes before that id gets written to status, so the next reconcile sees an empty status and calls create again, producing a duplicate. Closing this requires the external provider to accept an idempotency key, generated once and stored on the object before the first create call, so a retried create recognizes it already happened. _Engineers hardening operator create logic against crash-induced duplication can find patterns like this on daily.dev._ ### Why does a Kubernetes reconciler receive only a namespace and name instead of the full changed object? A reconciler is deliberately handed just a key (namespace and name) rather than the object itself, because by the time a worker pulls that key off the workqueue the object may have changed again. This forces the reconciler to always fetch current state itself instead of trusting whatever event triggered it, which is what makes the reconciliation loop resilient to missed or reordered events. _daily.dev helps developers piecing together Kubernetes controller internals like reconcile design decisions._ ## Similar posts on daily.dev - [Build Your Own Kubernetes Operators with Go and Kubebuilder](https://daily.dev/posts/build-your-own-kubernetes-operators-with-go-and-kubebuilder-lm0ntmppn) · freeCodeCamp · 110 upvotes · 0 comments - [Automating stateful apps with Kubernetes Operators](https://daily.dev/posts/automating-stateful-apps-with-kubernetes-operators-vxiwipjyc) · CNCF · 1 upvotes · 0 comments - [Kubernetes for developers: a complete beginner's guide](https://daily.dev/posts/kubernetes-for-developers-a-complete-beginner-s-guide-e5m8idnmp) · Flavio Copes · 2 upvotes · 0 comments - [Ten Years of the Operator Pattern: What We Got Right, What We’d Change](https://daily.dev/posts/ten-years-of-the-operator-pattern-what-we-got-right-what-we-d-change-qvwxglkrd) · Cloud Native Now · 3 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#golang](https://daily.dev/tags/golang) [View this post on daily.dev](https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How to Build Kubernetes Operators: A Handbook for Devs","url":"https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks"},"datePublished":"2026-07-29T16:20:36.845Z","dateModified":"2026-09-14T08:00:22.371Z","description":"A comprehensive guide to building Kubernetes operators from scratch, covering the full lifecycle from concept to production. Explains the difference between...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5acfa5e8c04f1f04462bbb437c889de8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5acfa5e8c04f1f04462bbb437c889de8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"freeCodeCamp","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Person","name":"Karan Pratap Singh","url":"https://daily.dev/karan_6864","image":"https://avatars1.githubusercontent.com/u/29705703?v=4","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":540}},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,golang","timeRequired":"PT29M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"freeCodeCamp","item":"https://daily.dev/sources/freecodecamp"},{"@type":"ListItem","position":3,"name":"How to Build Kubernetes Operators: A Handbook for Devs"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-to-build-kubernetes-operators-a-handbook-for-devs-9m9zoxqks#faq","mainEntity":[{"@type":"Question","name":"How do I stop a Kubernetes controller from reconciling in an infinite loop after it updates a resource's status?","acceptedAnswer":{"@type":"Answer","text":"Use a predicate that filters out status-only updates before they trigger a reconcile. Register builder.WithPredicates(predicate.GenerationChangedPredicate{}) in SetupWithManager, since the generation field only increments when spec changes, not status. This drops events where nothing but status moved, so the controller's own status writes stop retriggering itself, leaving only meaningful spec changes or explicit requeues to trigger reconciliation. daily.dev surfaces practical fixes like this for developers debugging their own operator reconcile loops."}},{"@type":"Question","name":"How can a Kubernetes operator avoid creating a duplicate external resource if it crashes right after creating it but before writing the status?","acceptedAnswer":{"@type":"Answer","text":"The gap happens because the external create call succeeds and returns an id, but the process crashes before that id gets written to status, so the next reconcile sees an empty status and calls create again, producing a duplicate. Closing this requires the external provider to accept an idempotency key, generated once and stored on the object before the first create call, so a retried create recognizes it already happened. Engineers hardening operator create logic against crash-induced duplication can find patterns like this on daily.dev."}},{"@type":"Question","name":"Why does a Kubernetes reconciler receive only a namespace and name instead of the full changed object?","acceptedAnswer":{"@type":"Answer","text":"A reconciler is deliberately handed just a key (namespace and name) rather than the object itself, because by the time a worker pulls that key off the workqueue the object may have changed again. This forces the reconciler to always fetch current state itself instead of trusting whatever event triggered it, which is what makes the reconciliation loop resilient to missed or reordered events. daily.dev helps developers piecing together Kubernetes controller internals like reconcile design decisions."}}]} ```