From kubernetes.io:
Ingress
FEATURE STATE: Kubernetes v1.19 [stable]
An API object that manages external access to the services in a cluster, typically HTTP.
Ingress may provide load balancing, SSL termination and name-based virtual hosting
So you have "middle-man between the client and the actual service" ...
You are right. Ingress is a middle-man between the client and the actual service but it's inevitable.
To make sure my app is highly available I must use a load balancer (ingress) which is a different component than an API gateway although modern load balancers might have some API gateway features.
Before I had client -> ingress -> gateway -> service. Now it's client -> ingress -> service.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From kubernetes.io:
Ingress
FEATURE STATE: Kubernetes v1.19 [stable]
An API object that manages external access to the services in a cluster, typically HTTP.
Ingress may provide load balancing, SSL termination and name-based virtual hosting
So you have "middle-man between the client and the actual service" ...
You are right. Ingress is a middle-man between the client and the actual service but it's inevitable.
To make sure my app is highly available I must use a load balancer (ingress) which is a different component than an API gateway although modern load balancers might have some API gateway features.
Before I had client -> ingress -> gateway -> service. Now it's client -> ingress -> service.