Run vs. Bridge Operation
| Run | Bridge | |
|---|---|---|
| What | Run a local container and connect it to a Kubernetes cluster | Build on top of run. Connect a local container to a Kubernetes cluster and reroute traffic to it |
| Multi-User | Multiple users can run multiple containers connected to the same cluster | Multiple users cannot bridge the same workload |
| When | When you want to test a service in the cluster or write code that depends on Kubernetes resources | When you want to expose a local container to other services within the cluster |
Run Operation
Run - allows to run a local container and connect it to a Kubernetes cluster. It is executed within a given namespace and can communicate with other services running in the cluster. This allows your local container to talk to things databases or internal APIs within the cluster you connected it to. Multiple users can run multiple containers connected to the same cluster.
TODO: Add Run Animation
Bridge Operation
Bridge - builds on top of Run. In certain situation you want other services to connect to your local container. For this, your local container
needs some kind of representation within the Kubernetes cluster it is connected to. With Bridge Gefyra patches a given workload within your
Kubernetes cluster and reroutes all the incoming traffic to your local container. Multiple users cannot bridge the same workload.
TODO: Add Bridge Animation
What is Gefyra?
Gefyra is a toolkit written in Python to organize a local development infrastructure in order to produce software for and with Kubernetes while having fun. It is installed on any development computer and starts its work when it is asked. Gefyra runs as a user-space application and controls the local Docker host and Kubernetes via Kubernetes Python Client.
What changed in Gefyra 2?
Operator - Gefyra's operator was completely refactored. It now acts as a state machine and shows much more stable and consistent behaviour. It manages 2 custom resources - GefyraClients and GefyraBridges.