-
|
Hi, I understand the architecture of Nginx Gateway Fabric includes Nginx Ingress in some capacity. But I don't see the same configuration options and items that Nginx Ingress had. I have legacy applications and ingress specifications for Nginx Ingress that rely on things like default TLS termination. Should I be running both? Nginx Ingress and Nginx Gateway Fabric? Will they compete with each other to own resources? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @avo-sepp, NGINX Gateway Fabric is independent of NGINX Ingress. While they both aim to solve the same use cases, they are different products with different APIs and configuration options. Therefore, they can both be deployed at the same time and will not conflict with each other. The current implementation of Gateway API may not 100% map to all Ingress use cases and options, since we are still developing the product. However, we have implemented some of the more important use cases. From a high level Gateway API perspective, you can read here to see how the two APIs are related. |
Beta Was this translation helpful? Give feedback.
Hi @avo-sepp, NGINX Gateway Fabric is independent of NGINX Ingress. While they both aim to solve the same use cases, they are different products with different APIs and configuration options. Therefore, they can both be deployed at the same time and will not conflict with each other.
The current implementation of Gateway API may not 100% map to all Ingress use cases and options, since we are still developing the product. However, we have implemented some of the more important use cases. From a high level Gateway API perspective, you can read here to see how the two APIs are related.