The fast, simple, and secure solution to k8s development.
Ready to go from the start - without any configuration or installations on the cluster.
Run the code in your IDE, get the breakpoint with the real traffic from your development namespace.
Break out of the CI dev loop, your changes are reflected on the cluster immediately.
Forget the "it works on my machine", the unreliable local-development mocks and hacks that let your app break when pushed to the cluster after you waited for the CI cycle.
*Supports Windows, Mac, Linux and WSL. Supports OpenShift.
Demo - Debug with the envilope flow
Select a service
The service will stop running in the cluster, and traffic will be diverted to the debugging host.
Run the service
You can do so in your IDE in debug mode, or whichever way you choose. Use the same port (8000 in this case)
The events we are debugging are usually received by the event-receiver on the cluster, but here, it is handled by us.
Behind the scenes
In the cluster, the pods of the service you chose will be replaced by an envilope tunneling pod. When done with debugging, the original deployment will be scaled back up.
Your own development suite
Keep working with all your beloved tools seamlessly integrated with our platform,
No need for extensive configuration – our solution ensures effortless compatibility,
so you can use tools like Postman, pgAdmin, and more, with your remote component and without interruption.
Test changes immediately
envilope allows you to see the changes to the code immediately, and only pass through the CI/CD pipeline when you've satisfied with your changes.
Avoid mistakes
Collaboration has never been easier with envilope. Our Kubernetes product is designed to ensure that the whole team can use it without stepping on anyone's toes.
With our user-friendly interface, you can easily collaborate with your team members.
1 minute setup
Getting started with envilope is quick and easy. With our simple installation process, you can be up and running in just 1 minute. We rely on your existing kubeconfig file to simplify the setup process.
Whether you're on Linux, Mac, Windows, or WSL, we've got you covered.
Under the hood
See the flow of the data: events are sent to the event-receiver service, which saves them to the database.
We want the flow to go through our computer, to solve the ongoing bug in the event-receiver.
The event receiver stops running on the cluster, and an envilope tunneling pod is created in its place.
Now, when you run the event-receiver source code, you'll be handling the same data the service was handling on the cluster, and saving to the same DB, utilizing the tunnels opened by envilope.
