Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Kong for Kubernetes 0.8 release provides consistent API management lifecycle

2025-04-05 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/02 Report--

The Kong API gateway is an open source API gateway based on NGINX. According to the announcement blog post, the Kong for Kubernetes product consists of two parts: one is the Kubernetes controller, which manages the Kong status of the K8S entry configuration, and the other is Kong Gateway, which is used to process and manage incoming API requests.

Most hosted Kubernetes deployments on the public cloud take advantage of Ingress controllers provided by cloud providers. These controllers can handle vendor load balancers and other computing abstractions. Kubernetes deployments can also choose to use other controllers, including NGINX and HAProxy.

There are media and Kong Inc. Reza Shafii, Vice President of products, contact for more information about this release and the general features of Kubernetes. Shafii explains that Kong for Kubernetes adds all the features of the Kong API gateway to Ingress. These are API management features, that is, the ability to "enable dynamic policy management of API traffic, such as OIDC-based authentication, advanced rate limiting, request caching, or simultaneous streaming of logs and metrics to different analysis providers".

Shafii further elaborates on performance aspects: these include high-performance profiles (for example, sub-millisecond latency and 25K + transactions per second) and support for multiple protocols and interaction modes (REST,graphQL,gRPC,TCP, etc.), while providing all operations through Kubernetes CRD: Kong Gateway. The last point is important because it will make the operational aspects of the portal consistent across all cloud providers and internal deployments.

According to Shafii, although Kong is built on top of nginx, its entry controller is significantly different from the default nginx-ingress-controller and nginx's own commercial controller. These differences lie in Kong's API management capabilities, and for Kong Gateway users, it provides a "consistent API management lifecycle" for both Kubernetes and non-Kubernetes workloads.

Version 0. 8 adds Ingress's support for Knative. Knative is a serverless platform on Kubernetes for container-based workloads that provides "a higher level of abstraction for common application use cases."

Knative's default Ingress is based on Istio, and there are other Gloo-like options. Shafii explains the difference between the default Ingress of Knative and the default Ingress provided by Kong: what I have learned from the community and customers is that most use cases do not require Istio to run serverless workloads. In fact, the heavy burden of Istio is one of the reasons that prompted us to start the Kuma services grid project.

Kong Gateway's plug-in architecture and focus on scalability help to make Knative workloads focus only on business logic, or you can use cloud provider load balancers with Kong's ingress controller.

Shafii fill in details: the cloud load balancer provides a way to balance traffic between multiple Kong Gateway nodes, and Kong Gateway nodes help manage traffic to multiple services within the cluster. In fact, for most users, we recommend using a load balancer (such as AWS or GCP's load balancer) to manage Kong Gateway. This provides an endpoint within the virtual private network in the cloud, which can then be exposed to other networks (different AWS accounts), other partner networks or directly on the Internet.

Similar to the network traffic metrics provided by cloud providers such as GCP and AWS and gateways such as Istio and Gloo, Kubernetes's Kong can collect "metrics such as HTTP status and error codes, traffic throughput / latency and (consumption / egress) bandwidth consumption". Each route and service level.

According to Shafii, the new version also provides health-related indicators for Kong Gateway itself, such as "connections to services, connections currently in use, shared memory usage, and cache hit ratios." He added that these metrics can be integrated with Prometheus,Data Dog,StatsD,Zipkin and Jaeger. Also, version 0.8 makes significant changes to path-based routing, and some comments are not recommended, and the update log has a complete list of changes.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report