--- title: Introducing mirrord up: Shared-Cluster Development in... description: mirrord up is a new command that simplifies shared-cluster Kubernetes development. Instead of manually composing mirrord.json config files and running separate... canonical: https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Introducing mirrord up: Shared-Cluster Development in One Command | daily.dev og:description: mirrord up is a new command that simplifies shared-cluster Kubernetes development. Instead of manually composing mirrord.json config files and running separate... og:url: https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke og:image: https://api.daily.dev/og/posts/iRk3pa2Ke.png og:image:alt: Introducing mirrord up: Shared-Cluster Development in One Command 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. # Introducing mirrord up: Shared-Cluster Development in One Command **[MetalBear](https://daily.dev/sources/metalbear)** · 4 min read · 10 upvotes · 0 comments ## Summary mirrord up is a new command that simplifies shared-cluster Kubernetes development. Instead of manually composing mirrord.json config files and running separate mirrord exec commands per service, developers now use a single mirrord-up.yaml file and one command. A --mode flag replaces complex mechanism combinations (HTTP filters, queue splitting, network modes), defaulting to 'split' mode which routes only your traffic to your local process. Multiple services can be run in parallel, similar to docker compose. An interactive wizard (mirrord up init) helps generate the config file. The existing mirrord exec workflow remains available for advanced use cases. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is mirrord up and how is it different from mirrord exec? mirrord up is a new command that replaces per-service mirrord.json configuration files and the mirrord exec workflow with a single mirrord-up.yaml file. Instead of manually composing mechanisms like HTTP filters, queue-splitting rules, and network modes, developers specify a use case such as --mode split, and mirrord automatically picks the right mechanisms. It also runs multiple services in parallel with one command, unlike mirrord exec which requires a separate terminal and command per service. _Teams evaluating local-to-cluster development workflows can track tooling changes like this on daily.dev._ ### How do I run multiple services at once with mirrord against a shared Kubernetes cluster? Define a map of services in a mirrord-up.yaml file, each with a run command, then execute a single mirrord up command. Mirrord launches a session for each service in parallel in the foreground, similar to how docker compose manages multiple containers, and pressing ctrl+c shuts them all down together. The file can be checked into a repo so every engineer gets the same setup without a custom launch script. _Developers standardizing multi-service local setups can follow tooling updates like this via daily.dev._ ## Similar posts on daily.dev - [How to Work with Server-Side Rendered Frontends Locally](https://daily.dev/posts/how-to-work-with-server-side-rendered-frontends-locally-pxx5xhhas) · MetalBear · 1 upvotes · 0 comments - [Running AI Agent Pools Against Your Live Kubernetes Cluster, with mirrord](https://daily.dev/posts/running-ai-agent-pools-against-your-live-kubernetes-cluster-with-mirrord-1rgeqa8yd) · MetalBear · 0 upvotes · 0 comments - [Federating clusters for zero-downtime Kubernetes](https://daily.dev/posts/federating-clusters-for-zero-downtime-kubernetes-zxxqifshs) · CNCF · 2 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#microservices](https://daily.dev/tags/microservices) [View this post on daily.dev](https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke) ```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":"Introducing mirrord up: Shared-Cluster Development in One Command","url":"https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke"},"datePublished":"2026-07-09T09:46:51.089Z","dateModified":"2026-09-14T08:13:52.904Z","description":"mirrord up is a new command that simplifies shared-cluster Kubernetes development. Instead of manually composing mirrord.json config files and running separate...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d8d9a40cfeee16b7b3872dee99085a7e?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d8d9a40cfeee16b7b3872dee99085a7e?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"MetalBear","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":"Organization","name":"MetalBear","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3165f5f876b147e2a160f4bf0fcaa13a","url":"https://daily.dev/sources/metalbear"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":10},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,microservices","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"MetalBear","item":"https://daily.dev/sources/metalbear"},{"@type":"ListItem","position":3,"name":"Introducing mirrord up: Shared-Cluster Development in One Command"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-mirrord-up-shared-cluster-development-in-one-command-irk3pa2ke#faq","mainEntity":[{"@type":"Question","name":"What is mirrord up and how is it different from mirrord exec?","acceptedAnswer":{"@type":"Answer","text":"mirrord up is a new command that replaces per-service mirrord.json configuration files and the mirrord exec workflow with a single mirrord-up.yaml file. Instead of manually composing mechanisms like HTTP filters, queue-splitting rules, and network modes, developers specify a use case such as --mode split, and mirrord automatically picks the right mechanisms. It also runs multiple services in parallel with one command, unlike mirrord exec which requires a separate terminal and command per service. Teams evaluating local-to-cluster development workflows can track tooling changes like this on daily.dev."}},{"@type":"Question","name":"How do I run multiple services at once with mirrord against a shared Kubernetes cluster?","acceptedAnswer":{"@type":"Answer","text":"Define a map of services in a mirrord-up.yaml file, each with a run command, then execute a single mirrord up command. Mirrord launches a session for each service in parallel in the foreground, similar to how docker compose manages multiple containers, and pressing ctrl+c shuts them all down together. The file can be checked into a repo so every engineer gets the same setup without a custom launch script. Developers standardizing multi-service local setups can follow tooling updates like this via daily.dev."}}]} ```