Modern API Gateway for Kubernetes workloads | Ingress 2.0 | DevOps | IMESH API Gateway

To overcome the challenges of handling north-south traffic in Kubernetes, DevOps and cloud teams must look out to transform their API gateway solution.
IMESH offers a low-code modern API gateway solution for Kubernetes which can be leveraged by DevOps and developers team without the learning curve. It is based on popular open-source ingress controllers- Istio and Envoy Gateway.
Key Features are:
1. Unified interface for API creation and management
2. RBAC for Routes and Gateway resource
3. Real-time dashboard for traffic analysis
4. Conformance with Gateway API specs by CNCF
5. Highly scalable
The IMESH API gateway offers a Kubernetes-native ingress controller for DevOps and developers to overcome application networking's limitations. It is based on Envoy Proxy, which makes it faster and lighter. It conforms to Kubernetes Gateway API specifications. Unlike legacy gateway solutions, the IMESH API gateway is meant to handle traffic at scale for microservices-based applications.
➡️ To know more about the product: imesh.ai/imesh...
➡️ Join the IMESH Slack: imesh.ai/regis...
➡️ Install IMESH API Gateway for free: docs.imesh.ai/
For more watch-
➡️ How to Install IMESH API Gateway in your Kubernetes Cluster: • How to Install IMESH A...
➡️ How to create Gateways using IMESH API Gateway: • How to create Gateways...
➡️ How to create Routes using IMESH API Gateway: • How to create Routes u...
➡️ How to Get Started with IMESH API Gateway 1.0 for Kubernetes: • How to Get Started wit...
▬▬▬▬▬ Additional resources ▬▬▬▬▬▬
➡️ IMESH API Gateway Release Hydra 1.0: imesh.ai/blog/...
➡️ Learn Istio service mesh from scratch in 3 hrs: www.udemy.com/...
➡️ Looking for Istio at scale, without any of its operational complexities? Check this out: imesh.ai/manag...
▬▬▬▬▬ About IMESH ▬▬▬▬▬▬
IMESH offers a Kubernetes-native application network and security platform to manage multi-cloud and hybrid-cloud environments. The IMESH platform is built on top of Istio service mesh and Envoy API gateway and helps cloud, platform, and security teams to make Kubernetes applications more secure, manageable, and reliable.
▬▬▬▬▬ Connect ▬▬▬▬▬▬
Website: imesh.ai/
GitHub: github.com/ime...
LinkedIn: / imeshai
▬▬▬▬▬▬ Thanks ▬▬▬▬▬▬
#api #istio #apigateway #imesh

[@josephwagner6682]

Hi
Thanks for running us through the whole process.
But please help me to understand the added value of the Imesh portal?
Considering GitOps is the golden standard, creating things with a UI is not the best practice.
The best practice here would be to use ArgoCD or any other CI/CD tool to apply this gateway and route manifests by syncing with a git repo.
All things you did via UI can be achieved by applying a simple k8s manifest, so why add cloud cloud-based service to your setup.
Furthermore one would expose his microservices directly via public IP on the Loadbalancer to the internet meaning that these LBs IPs should not be accessible from the internet at all.
So I'm wondering what use case would make use of this imesh cloud service offering legit ?
BR
Joseph

[@imesh.ai_inc]

Thanks, Joseph.
You have rightly pointed out that GitOps is essential. And we do 100% support GitOps.
IMESH Platform supports two deployment models- GitOps-based and direct deployment.
For GitOps-based, the IMESH platform translates the UI form into YAML. After that, the usual GitOps-style delivery process is initiated with software like Argo CD.
For startups and lower environments- where the concept of CI/CD or GitOps is not yet practiced, IMESH API gateway would be handy for them to easily create and manage north-south traffic in the cluster from the simple UI with direct deployment option.
Reasons for our low-code platform are:
1. Many developer teams think it is a context switch to learn YAML.
2. Creating network resources and policies involves a high learning curve (as one must remember all configurations).
3. Creation/editing of manifests often leads to errors & debugging issues, which is counter-productive.
4. Enhance the visibility of all the network resources in a single pane of glass.
5. The DevOps and cloud team would know who created/managed what resources.
6. Real-time view of performance of network resources with just one click.

[@debasreepanda5387]

Regarding public IP concerns, the IMESH platform does not need any public IP to be exposed in the client cluster. It works in reverse.