Subscribe
Sign in
mirrord for Teams — Remocal Kubernetes development for teams and enterprises
mirrord solves the problems every modern cloud developer faces during microservice development by making remote services feel local.
71
Replies
Best
@max_savonin1 Hey Max, thanks for the feedback!
To answer your questions:
- mirrord for Teams includes a centralized component in the cluster called the mirrord Operator, which mediates the functionality of all mirrord clients. It uses the existing Kubernetes RBAC to limit what users can and can't do.
- The mirrord CLI makes it easy to integrate with CI/CD, and a lot of our users use it to speed up test suites by using an existing persistent cloud environment instead of spinning one up and down for each run.
Thanks again!
How does it handle scale? Have you seen it being used in clusters with 100s+ pods?
Congrats on the launch 🎉👏
@maritamar Thanks! Since all the meaty stuff - proxying logic between the client and the cluster - happens at the process level, mirrord is pretty much agnostic to scale. We've seen it working in clusters with 1000s of pods without breaking a sweat 😉
It really makes the developer's life easier. No more pushing WIP code and waiting for the pipeline to finish.
💎 Pixel perfection
Been an early adapter of mirrord and our workflows have completely changed thanks to their team. I was looking for something like this for a while and the alternatives had many cons that stopped us from using it.
The MetalBear team had a different approach that really changed the game.
If you have a cluster, just give it a go and see how simple it is by yourself.
So excited for you guys! Long journey that eventually comes into an impressive product that every developer team/individual should adapt in own environment.
Super excited for the release of mirrord for teams, I love the ability to work on same environment with my teammates without blocking/overriding each other with changes even if we are working on the same service !!!
Already been using Mirrord for a while now, it has made my development workflow so simple that I can't go back to deploying commits. So was very happy to see this launch today :) Great work guys!
💎 Pixel perfection
Debugging has never been this easy
Faster feedback loops
- Spend less time building, containerizing, and deploying code.
- Get immediate feedback on code changes by running your service in the cloud from your local machine.
Debug locally like your in the cloud
- Use your favourite IDE, debugger, and other tools locally.
- Improved developer experience
Shift testing left
- Test your code changes in a production-like environment before merging to main.
Simplify local development
- Eliminate the need for complex infrastructure setup and maintenance locally.
- Pull the repo down and begin coding.
- No need to mock services or run a local version of your cloud infrastructure.
Not only is the tool truly amazing and has made life so much easier!!!
But the team is world class, professional, and a joy to work with.
I would highly recommend for Teams or personal projects.
Daily driving mirrord in my RnD team for a long time. This is an amazing product that made our lives so much easier. Huge shoutout to everyone involved!
Super helpful in allowing my team to push and test updates, it's not only easier to manage but the end result is accelerating our product GTM timeline for new features.
This sounds like a game-changer for Kubernetes developers! How does the security setup work when using mirrors for Teams?
@memphys_sk Thanks! mirrord for Teams includes a cluster component called the mirrord Operator which uses existing Kubernetes RBAC to allow or disallow user actions. In addition, mirrord for Teams includes a feature called mirrord Policies, where admins can manage exactly which actions users can perform with mirrord.
Oh that's cool!
Question though - How does it support concurrent debugging of the same pod?
@eyal_solomon Thanks! So the easiest way to debug the same pod concurrently is to mirror traffic - then everyone working on a pod gets a duplicate of its incoming traffic, but it's the pod itself that answers requests.
But what if you want every request to only be handled once? That's where the HTTP filtering feature comes in, which lets you only receive traffic locally matching a certain header, and be the one to respond to it as well.
mirrord