kuma | zone service mesh for containers , Kubernetes and VMs | Service Mesh library

The paginate method, runs an implicit get on your query result. try to use withQueryString instead of paginate. example:

Had the same issue, after days of looking for a solution, I came across metallb, from nginx ingress installation on bare metal

MetalLB provides a network load-balancer implementation for Kubernetes clusters that do not run on a supported cloud provider, effectively allowing the usage of LoadBalancer Services within any cluster

, from their documentation I got this

Kubernetes does not offer an implementation of network load balancers (Services of type LoadBalancer) for bare-metal clusters. The implementations of network load balancers that Kubernetes does ship with are all glue code that calls out to various IaaS platforms (GCP, AWS, Azure…). If you’re not running on a supported IaaS platform (GCP, AWS, Azure…), LoadBalancers will remain in the “pending” state indefinitely when created.

I didn't finalize the installation but I hope the explanation above answers your question on pending status on external ip

You can delete Kuma with almost the same command you used to install it.

First of all you have to use findone to get one row, you can do something like:

For remote development/debugging I would suggest to have a look at Telepresence.

https://www.telepresence.io/

It is even recommended by Kubernetes docs:

Using telepresence allows you to use custom tools, such as a debugger and IDE, for a local service and provides the service full access to ConfigMap, secrets, and the services running on the remote cluster.

https://kubernetes.io/docs/tasks/debug-application-cluster/local-debugging/

Istio on the other hand enables you to do shadow deployment and canary or blue/green deployment. You can e.g. run a service and send certain user (based on the header) to a new version. You can mirror traffic to a service or shift traffic from 0 to 100 % step by step. I'd say it's more for testing your new service under load or gradually releasing a new version.

Kuma defines the so-called zone as a domain of control isolation, i.e. all workload connections are managed by a single control plane. Such a control plane is called remote. The overall view and policy management is done in a global control plane, which unifies all zones.

When one starts planning a distributed deployment, they have to enlist the following items:

• Where the Global control plane will be deployed and its type. The latter can be either Universal (VM/BareMetal/Container) or Kubernetes(on-premise/cloud).
• Number and type of zones to add. These can be changed over time.

Follow the instructions to install the global control plane following the steps specific for the chose type of deployment. Gather the relevant IP address/ports as described.

Installing remote control plane is fairly trivial. This process can be repeated as needed during the lifetime of the whole multi-zone deployment.

Cross-zone service consumption is described in brief here. In short, we do recommend using the following syntax to access a service echo-server, deployed in a Kubernetes namespace echo-example and exposed on port 1010:

You can use file_exists() function to check if the file exists.