How does our team use KubeOrbit to improve development and feedback cycle?

A growing number of organizations have completed their cloud-native transformation and migrated services to Kubernetes, gaining better resource utilization and the ability to meet expanding demands. Simultaneously, problems emerged due to the increase in system complexity. The developers have to submit a CI/CD for each modification and verification. A set of methods are required to achieve rapid and efficient development, connecting the remote Kubernetes cluster and the local environment, shortening the time for running feedback and debugging.

KubeOrbit CLI
As an open source integration testing tool, KubeOrbit CLI enables developers to program and test microservices locally for remote Kubernetes clusters easily and independently. This allows developers to collaborate, debug and get faster feedback.

KubeOrbit CLI is designed with excellent compatibility for different situations. It supports native Kubernetes SVC service discover, as well as Eureka, Nacos, Consul and other mainstream microservice registry and discovery centers. (See the picture above.)

Main Function Forward Command:
The Forward command is primarily used to direct traffic from the remote cluster to the local. You can directly access the local service from the cluster. You can configure the container's three-layer routing forwarding rules by deploying the Proxy Agent in the cluster. At the same time, you can set up ssh port forwarding with the local CLI tool, this way, a tunnel will be successfully established between the ssh client and the server. Forward uses the ssh remote port forwarding method, which involves forwarding the request sent to the remote host port to the target host, so that we can access the target host port via the remote port.
After executing Forward command, you will see that the Traffic Agent has been injected. (See the picture above [Traffic Agent]).

The detailed workflow is as follows:

1. Restart the Workload Pod
2. Initialize the container to start and configure the Pod network stack
3. The proxy container kubeorbit-proxy is successfully injected
4. Execute port-forward to map the remote service port to the local ssh port
5. Execute ssh remote port forwarding to forward traffic to the local designated service's port.

Presently, the KubeOrbit CLI cross-platform operating system already supports Mac, Linux, and Windows. The current version only provides the ability to connect from remote to local clusters. In the future, we'll keep optimizing its functions, the connection from local to remote clusters and intranet DNS will be integrated as needed.

Know more: www.kubeorbit.io
Drop your resume: hr@teamcode.com
Contact us: dev.relation@teamcode.com