eyalbukchin

6 ms·

1.
The AI-Native SDLC Starts with Your Infrastructure(metalbear.com)
1 points by eyalbukchin 1mo ago|0 comments
2.
Using mirrord to verify AI-SRE fixes against the staging cluster(metalbear.com)
2 points by eyalbukchin 3mo ago|0 comments
3.
by eyalbukchin 4mo ago
(CTO of mirrord here.) "Running specific services locally while leaving the rest in the cloud" is exactly it, but it's not as simple as you make it sound. At monday's scale you have large DB state and too many microservi
4.
by eyalbukchin 2y ago
Not only do more bugs reproduce in staging than locally (for obvious reasons), but mirrord also saves you the trouble of figuring out how to run your stuff locally in the first place. Previously, before you could add a single line of code t
5.
Comparing Local Kubernetes Development Tools(kubernetes.io)
2 points by eyalbukchin 3y ago|0 comments
6.
by eyalbukchin 4y ago
Ideally! And it can be run on a Linux machine if the user prefers. But if you code on a Mac, mirrord still lets you go through a good number of test iterations (by letting your process run with network input/output, file content and en
7.
by eyalbukchin 4y ago
It's initially the parent who'll pick the book though (or the critic? the people who decide what to put in the front window of the bookstore? probably not the four year old though), so the uncanniness could come into play.
8.
by eyalbukchin 4y ago
This is detailed in the post, but the security feature i.e. preventing injected libraries access to entitlements isn't actually bypassed here. Rather the binary is run without these entitlements (which aren't required anyway for m
9.
by eyalbukchin 4y ago
Maybe, we haven't looked into that option for the following reasons: a. It would require that we maintain a potentially pretty big list of self-compiled binaries b. It would be an alteration of what the user's running, which we tr
10.
by eyalbukchin 4y ago
The part of mirrord that's affected by SIP is the client. This is meant to be run by users on their development machines (we could ask them to disable SIP, but would rather not for obvious reasons).
11.
Show HN: mirrord – run your local code in the context of your cloud environment(mirrord.dev)
24 points by eyalbukchin 4y ago|0 comments
12.
by eyalbukchin 4y ago
It does work with any k8s cluster, no operator needed. It indeed relies on kubectl's config to talk to the k8s API. All that's needed is permissions to run privileged pods (or if you've configured mirrord to use ephemeral con
13.
Hooking Go from Rust – Hitchhiker’s Guide to the Go-Laxy(metalbear.co)
7 points by eyalbukchin 4y ago|0 comments
14.
by eyalbukchin 4y ago
So there are a bunch of use cases, but the main one we think is during day to day development. mirrord can give you access to “cloud conditions” while you code, without having to go through CI and actually deploying, which a. makes your fee
15.
by eyalbukchin 4y ago
First of all, mirrord runs on the process level. Telepresence either runs on your local machine, changing its network behavior or in a container making development less smooth than running a local process. Second, mirrord's default is
16.
by eyalbukchin 4y ago
Our agent sniffs traffic in the same network namespace as the pod whose incoming traffic we mirror, so in most cases that would be after the HTTPS traffic is decrypted (by e.g. a load balancer, or a service mesh)
17.
by eyalbukchin 4y ago
Up to you: you’re going to be able to configure what works locally vs what works with the cloud environment. So for example, you could configure all read functionality (incoming traffic, DB reads) to work with the cloud, and all write funct
18.
by eyalbukchin 4y ago
Yes! This is actually in development at the moment so should be out really soon. Along that same line, we're also planning to support routing of outgoing traffic back to the cloud environment. We're obviously thinking of both thos