You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a feature to support containerized workloads which would run user's workload in containers like docker and local agent would run in the same container/ same network using docker compose. Port forward happens from user's workload to local agent to remote agent running the k8s cluster and vice versa.
Pros:
Eliminates the need of elevated permissions
Doesn't harm local machines configurations
Resolves conflicts with services already running in any port which B2K might allocate ex: port 80, 443.
Cons:
user workloads need to be containerized in local, ex: running in a container in docker
This is actually the dev environment that my company uses. Using vscode and docker desktop with kubernetes enabled. We have a dev-container setup, then we use that to b2k into whatever pod we need to.
We did have to build all the arm64 things mentioned in #273 to get it to work for our arm macs.
It is handy because it enables us to debug against a production like environment. The drawback is it needs a good amount of memory. Also debugging against React can get kind of glitchy sometimes. It also occasionally runs into a resource issue that causes the kubernetes pods to go into an evicted or completed state.
This is a feature to support containerized workloads which would run user's workload in containers like docker and local agent would run in the same container/ same network using docker compose. Port forward happens from user's workload to local agent to remote agent running the k8s cluster and vice versa.
Pros:
Cons:
The text was updated successfully, but these errors were encountered: