MetalBear, creator of open source Kubernetes development solution mirrord, is introducing mirrord for CI, a breakthrough capability that brings production-like context from real environments directly into continuous integration (CI) pipelines.
According to the company, with mirrord for CI, engineering teams can run their entire CI test suite against a single shared, production-like Kubernetes environment without deploying code and without spinning up expensive and complex replica environments.
As cloud-native architectures become more distributed, the gap between CI test environments and production systems widens release risk, especially in Kubernetes-based microservice architectures, the company said.
mirrord for CI extends mirrord’s environment-mirroring technology into CI workflows, allowing CI runners to securely connect to an organization’s Kubernetes environment and execute tests using real services, dependencies, environment variables, and network conditions.
mirrord ensures all tests run with strict isolation to ensure no impact on target environments, such as staging. This capability delivers production-accurate validation without the overhead of deploying code or maintaining ephemeral clusters.
“CI pipelines rely on isolation, which forces teams to spin up separate test environments,” said Aviram Hassan, CEO and co-founder of MetalBear. “That adds spin-up time, increases complexity, and still doesn’t reflect production, so teams end up paying the price after deployment. With mirrord for CI, we’re introducing a new category: real-environment CI. Teams validate code against an already-running Kubernetes environment, eliminating spin-up time while safely testing in real production-like context and fundamentally raising the bar for how cloud-native software is tested and shipped.”
By unifying local development, CI, and production-like context into a single, consistent workflow, mirrord for CI introduces what MetalBear calls real-environment CI. This approach increases test fidelity and accelerates delivery cycles without changing existing workflows or duplicating infrastructure, giving teams greater confidence in every release, said MetalBear.
For more information about this news, visit https://metalbear.com.