Friday, October 7, 2022
HomeJavaA fast look on the Kubernetes Gateway API

A fast look on the Kubernetes Gateway API


Exterior entry to Kubernetes pods went via a number of evolutionary steps, e.g., Ingress is the reply to the issue of the shortage of routing in LoadBalancer. The most important situation of Ingress is its dependency on “proprietary” objects. As a reminder, right here’s the snippet to create routing utilizing Apache APISIX:

apiVersion: apisix.apache.org/v2beta3            (1)
type: ApisixRoute                                (1)
metadata:
  title: apisix-route
spec:
  http:
  - title: left
    match:
      paths:
      - "/left"
    backends:
      - serviceName: left
        servicePort: 80
  - title: proper
    match:
      paths:
        - "/proper"
    backends:
      - serviceName: proper
        servicePort: 80

Proprietary objects are an issue when migrating. Whereas migration from one supplier to a different might be unusual, it needs to be as seamless as attainable. When utilizing proprietary objects, you first have to map from the outdated object to the brand new ones. Likelihood is that it’s not a one-to-one mapping. Then, it’s essential translate the specification into the brand new mannequin: it’s more likely to be a full-fledged undertaking.

The concept behind the Gateway API is to have a clear separation between normal objects and the proprietary implementation.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments