Feature Request: Implement Gateway API Support
With the impending end-of-life for ingress-nginx support in Kubernetes, it's crucial for us to transition to the Gateway API for ingress management. This feature request proposes adding support for HTTPRoute resources within our templates.
The implementation should include:
HTTPRoute Template Integration: Introduce HTTPRoute definitions into our existing templating system.
Toggle for Gateway API: Provide a configuration option to enable Gateway API support.
ingress-nginx Disablement: When Gateway API is enabled, automatically disable the deployment and configuration of ingress-nginx resources.
Conditional ingress-nginx Dependency: Ensure that ingress-nginx is no longer a required dependency when Gateway API is active.
Rationale
Adopting the Kubernetes Gateway API is a critical step for maintaining a secure and future-proof secret management solution. As a secret manager, security is paramount, and aligning with Kubernetes' evolving best practices for traffic management is essential. The Gateway API offers a more robust, extensible, and role-oriented approach to ingress, which directly benefits the security and operational stability of our deployments.
Additional Context
For further information on the deprecation of ingress-nginx and the benefits of the Gateway API, please refer to the following resources:
Ingress-Nginx Retirement Announcement
Kubernetes Gateway API Documentation
Feature Request: Implement Gateway API Support
With the impending end-of-life for ingress-nginx support in Kubernetes, it's crucial for us to transition to the Gateway API for ingress management. This feature request proposes adding support for HTTPRoute resources within our templates.
The implementation should include:
HTTPRoute Template Integration: Introduce HTTPRoute definitions into our existing templating system.
Toggle for Gateway API: Provide a configuration option to enable Gateway API support.
ingress-nginx Disablement: When Gateway API is enabled, automatically disable the deployment and configuration of ingress-nginx resources.
Conditional ingress-nginx Dependency: Ensure that ingress-nginx is no longer a required dependency when Gateway API is active.
Rationale
Adopting the Kubernetes Gateway API is a critical step for maintaining a secure and future-proof secret management solution. As a secret manager, security is paramount, and aligning with Kubernetes' evolving best practices for traffic management is essential. The Gateway API offers a more robust, extensible, and role-oriented approach to ingress, which directly benefits the security and operational stability of our deployments.
Additional Context
For further information on the deprecation of ingress-nginx and the benefits of the Gateway API, please refer to the following resources:
Ingress-Nginx Retirement Announcement
Kubernetes Gateway API Documentation