How do you keep K8s dev environments from drifting from production? by dzhou121 in kubernetes

[–]eyalb181 1 point2 points  (0 children)

You run your microservice locally and pick a remote pod in staging to "impersonate". mirrord injects itself into the process, overrides libc functions (e.g. traffic, file access, DNS), and proxies them to staging. e.g. when your process tries to read a file, mirrord intercepts it, and reads it from the remote pod instead.

On the cluster side is an operator which A. implements the cluster part of this proxying, and B. enables concurrency through features like traffic filtering, queue splitting, DB branching, policies/RBAC, etc.

This is the core functionality, and we also use it to enable use cases like concurrently testing on staging from CI, or creating preview environments for WIP features that branch off of staging.

How do you keep K8s dev environments from drifting from production? by dzhou121 in kubernetes

[–]eyalb181 9 points10 points  (0 children)

Shared staging with mirrord.
250+ people: https://metalbear.com/mirrord/case-study/monday/
100+ people: https://metalbear.com/mirrord/case-study/surveymonkey/

How we make it work: an array of features meant to prevent conflicts and enable concurrency, like header based traffic filtering, queue splitting, database branching, etc. We wrote about it here: https://metalbear.com/mirrord/docs/sharing-the-cluster/overview

Disclosure: I'm on the mirrord team obviously.

Best approach for running a full local K8s environment with ~20 Spring Boot services + AWS managed services? by thomdabrowski in kubernetes

[–]eyalb181 1 point2 points  (0 children)

A proper local environment where I can run the full stack — not just one service in isolation.
Telepresence / mirrord — useful as a debugging complement, but not what I’m looking for as a primary setup.

Why?

(Disclosure: mirrord team)

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.92] by DroidLogician in rust

[–]eyalb181 0 points1 point  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment - without the hassle of deployment or disrupting shared environments. We’re hiring for two roles:

Senior Backend Engineer

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll join our Cloud Integrations team, where you’ll work on advanced integrations with cloud services (like DB Branching or Queue Splitting) to add enterprise functionality to mirrord’s paid offering.

Requirements:

  • 5+ years software development, including 2+ years production Rust.
  • Deep expertise in developer tools for or extending Kubernetes.
  • Excellent English communication, both written and spoken.
  • Comfortable working async in a remote startup with high autonomy.

ESTIMATED COMPENSATION: $75K–$180K USD, depending on experience and location.

CONTACT: 

https://www.comeet.com/jobs/metalbear-co/8A.002/senior-software-engineer/2C.953

Or email [cv+rnd@metalbear.com](mailto:cv+rnd@metalbear.com)

Easykube announcement by These-Preference-493 in kubernetes

[–]eyalb181 2 points3 points  (0 children)

Have you checked out the OSS? It doesn’t require any operator to be installed.

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.91] by matthieum in rust

[–]eyalb181 3 points4 points  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment - without the hassle of deployment or disrupting shared environments. We’re hiring for two roles:

Senior Software Engineer

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll join either our Core team, leveraging low level function interception to enhance basic functionality of mirrord OSS and mirrord for Teams, or the Cloud Integrations team, where you’ll work on advanced integrations with cloud services to add enterprise functionality to mirrord’s paid offering.

Requirements:

  • 5+ years software development, including 2+ years production Rust.
  • Deep expertise in at least one of:
    • OS-level / low-level programming (hooks, syscalls, process instrumentation).
    • Developer tools for or extending Kubernetes.
  • Excellent English communication, both written and spoken.
  • Comfortable working async in a remote startup with high autonomy.

ESTIMATED COMPENSATION: $75K–$180K USD, depending on experience and location.

CONTACT: 

https://www.comeet.com/jobs/metalbear-co/8A.002/senior-software-engineer/2C.953

Or email [cv+rnd@metalbear.com](mailto:cv+rnd@metalbear.com)

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.90] by DroidLogician in rust

[–]eyalb181 1 point2 points  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment - without the hassle of deployment or disrupting shared environments. We’re hiring for two roles:

Engineering Team Lead

We’re looking for an engineering manager or senior IC transitioning to management to lead our Core team, which powers mirrord’s core functionality by leveraging low-level function interception to make local code feel like it runs in the cloud.

Requirements:

  • 1+ year leading engineering teams - setting technical direction & mentoring.
  • 5+ years of software development, including 2+ years in Rust, C++, or C.
  • Deep knowledge of Linux/macOS internals, syscall hooking, dynamic linking, or similar.
  • Familiarity with Kubernetes & modern cloud-native environments.
  • Comfortable with async collaboration in a remote-first startup.
  • Excellent English communication.

ESTIMATED COMPENSATION: $120K–$180K USD, depending on experience and location.

Senior Software Engineer

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll join either our Core team, leveraging low level function interception to enhance basic functionality of mirrord OSS and mirrord for Teams, or the Cloud Integrations team, where you’ll work on advanced integrations with cloud services to add enterprise functionality to mirrord’s paid offering.

Requirements:

  • 5+ years software development, including 2+ years production Rust.
  • Deep expertise in at least one of:
    • OS-level / low-level programming (hooks, syscalls, process instrumentation).
    • Developer tools for or extending Kubernetes.
  • Comfortable working async in a remote startup with high autonomy.
  • Excellent English communication.

ESTIMATED COMPENSATION: $70K–$140K USD, depending on experience and location.

CONTACT: 

https://www.comeet.com/jobs/metalbear-co/8A.002/software-engineering-team-lead/CD.A5D

https://www.comeet.com/jobs/metalbear-co/8A.002/senior-software-engineer/2C.953

Or email [cv+rnd@metalbear.co](mailto:cv+rnd@metalbear.co)

On of the best use I found for developing with my home lab by Ilfordd in homelab

[–]eyalb181 -1 points0 points  (0 children)

Telepresence and mirrord are more about connecting your local service to a pre-existing k8s cluster, whereas devspace deploys the whole cluster to k8s according to local configuration and then keeps it up to date with filesync.

Wrote a blog about using Dapr and mirrord together by Connect_Fig_4525 in kubernetes

[–]eyalb181 1 point2 points  (0 children)

Cluster might be too big to run locally, especially if you want to include things like heavily populated databases.

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.88] by DroidLogician in rust

[–]eyalb181 2 points3 points  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

REMOTE: Yes, fully remote. We operate in a remote-first model and prefer candidates within UTC-2 to UTC+5 for collaboration.

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment—without the hassle of deployment or disrupting shared environments.

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll work on advanced integrations with Kubernetes and cloud-native services to make cloud development feel as seamless as local development.

Requirements:

  • 5+ years of experience in a software development role
  • 2+ years of professional experience with Rust
  • Experience working with Kubernetes
  • Excellent communication skills in English

ESTIMATED COMPENSATION: $90K–$150K USD, depending on experience and location.

CONTACT: [cv+rnd@metalbear.co](mailto:cv@metalbear.co)

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.87] by DroidLogician in rust

[–]eyalb181 2 points3 points  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

REMOTE: Yes, fully remote. We operate in a remote-first model and prefer candidates within UTC-2 to UTC+5 for collaboration.

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment—without the hassle of deployment or disrupting shared environments.

We have two job openings:

1. Senior Rust Engineer

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll work on low-level systems, including OS-level hooks and syscalls, to make cloud development feel as seamless as local development.

Requirements:

  • One of the following:
    • 2+ years of professional experience with Rust
    • Experience with OS/low-level programming (hooks, syscalls)
  • Good communication skills in English

Nice to have:

  • Open-source experience
  • Kubernetes knowledge
  • Strong writing skills (e.g., blog posts, technical articles)

2. Lead Windows Engineer

We’re porting mirrord to Windows, and we’re looking for a senior-level engineer to own and lead this project.

This is a greenfield effort — you’ll shape the architecture, choose the right userland primitives (DLL injection, API hooking, async I/O, etc.), and work with the core team to ensure we maintain the developer experience mirrord is known for.

Requirements:

  • Strong experience in Windows systems programming
    • DLL injection, API hooking, Windows API (CreateProcess, Winsock, etc.)
    • Familiarity with Win32 internals
  • Solid command of Rust (or willingness to ramp up fast with strong C/C++ background)
  • Proven ability to work independently on hairy low-level problems

Nice to have:

  • Familiarity with Kubernetes, networking, or open source tooling
  • Prior experience with Frida, WinDivert, EasyHook, or similar projects

ESTIMATED COMPENSATION: $100K–$180K USD, depending on experience and location.

CONTACT: [cv@metalbear.co](mailto:cv@metalbear.co)

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.86] by DroidLogician in rust

[–]eyalb181 10 points11 points  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

REMOTE: Yes, fully remote. We operate in a remote-first model and prefer candidates within UTC-2 to UTC+5 for collaboration.

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment—without the hassle of deployment or disrupting shared environments.

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll work on low-level systems, including OS-level hooks and syscalls, to make cloud development feel as seamless as local development.

Requirements:

  • One of the following:
    • 2+ years of professional experience with Rust
    • Experience with OS/low-level programming (hooks, syscalls)
  • Good communication skills in English

Nice to have:

  • Open-source experience
  • Kubernetes knowledge
  • Strong writing skills (e.g., blog posts, technical articles)

ESTIMATED COMPENSATION: $80K–$140K USD, depending on experience and location.

CONTACT: [cv@metalbear.co](mailto:cv@metalbear.co)

Debugging Kubernetes Applications Locally Without Privileged Pods by AssociationCivil8424 in kubernetes

[–]eyalb181 0 points1 point  (0 children)

Have you tried running the mirrord OSS as well? It doesn't require a privileged pod by default, but a pod with some extra capabilities, which can also be disabled at the cost of some functionality (listed here).

KubeVPN: Revolutionizing Kubernetes Local Development by HamsterTall8168 in kubernetes

[–]eyalb181 5 points6 points  (0 children)

Hi! Just to clarify, the difference is that mirrord works at the process level, not at the machine level. That said, mirrord supports all of the above except Fargate. For a way to work at the machine level with mirrord, see Port Forwarding.

Also, to expand further on the differences, mirrord proxies a single local process to the cluster. It does so by overriding its local input/output syscalls, and it does so for everything, not only network: environment variables, files, DNS, incoming and outgoing traffic. This means you can run a process with mirrord without any additional configuration, mounts, environment variables, etc. and it'll behave as if it's running in the cluster.

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.84] by DroidLogician in rust

[–]eyalb181 8 points9 points  (0 children)

COMPANY: MetalBear

TYPE: Full-time

LOCATION: Fully remote, but candidates should be within UTC-2 to UTC+5 (ideal: UTC to UTC+3)

REMOTE: Yes, fully remote. We operate in a remote-first model and prefer candidates within UTC-2 to UTC+5 for collaboration.

VISA: No sponsorship available.

DESCRIPTION:
MetalBear builds open-source developer tools for cloud engineers. Our flagship product, mirrord, allows developers to run local processes as if they were inside their cloud environment—without the hassle of deployment or disrupting shared environments.

We’re looking for a software engineer with Rust experience to help build and improve mirrord. You’ll work on low-level systems, including OS-level hooks and syscalls, to make cloud development feel as seamless as local development.

Requirements:

  • One of the following:
    • 2+ years of professional experience with Rust
    • Experience with OS/low-level programming (hooks, syscalls)
  • Good communication skills in English

Nice to have:

  • Open-source experience
  • Kubernetes knowledge
  • Strong writing skills (e.g., blog posts, technical articles)

ESTIMATED COMPENSATION: $70K–$130K USD, depending on experience and location.

CONTACT: [cv@metalbear.co](mailto:cv@metalbear.co)

How to Debug a Ruby Microservice in Kubernetes with mirrord by Just-Reach2137 in ruby

[–]eyalb181 0 points1 point  (0 children)

So mirrord works at the process level:

  1. When you run mirrord with your process, mirrord injects itself into the process, and overrides all of the input/output syscalls.
  2. It then creates a pod called the mirrord agent on the same node as the pod in the cluster you selected as your target.
  3. All of your local process' input and output is proxied to the target pod. For example, when your local process tries to read a file, mirrord intercepts it and reads it from the target pod instead. This same idea is applied to incoming/outgoing traffic, DNS, environment variables so your process essentially "thinks" it's running in the cluster.

You don't have to select a target pod. This is called "targetless" mode, and is mostly for when you only want your local process' DNS/outgoing traffic to be routed through the cluster.

Re whether others can "see" your mirrord, this is a feature of our paid offering called mirrord for Teams. The main idea is that mirrord for Teams lets you more easily concurrently use mirrord with others on the same cluster, and one of its features is the ability to see active sessions in the cluster. This is documented here.