Enable CORS releated capabilities in `kind: Ingress`

[shaun-nx]

Overview

When configuring CORS (Cross Origin Resource Sharing) in NGINX Ingress Controller today, it is possible through response and request header manipulation in VirtualServer

For example

responseHeaders:
  add:
    - name: Access-Control-Allow-Credentials
      value: "true"
    - name: Access-Control-Allow-Headers
      value: "X-Forwarded-For"
    - name: Access-Control-Allow-Methods
      value: "PUT, GET, POST, OPTIONS"
    - name: Access-Control-Allow-Origin
      value: "*"
    - name: Access-Control-Max-Age
      value: "seconds"

The goal of this issue is to allow users to configure these same headers with kind: Ingress

Acceptance Critera

• Expose annotations to configure CORS related headers
• Ensure annotations are validated

References

See here for how ingress-nginx annotations are set, and how they map to VirtualServer: https://docs.nginx.com/nginx-ingress-controller/installation/ingress-nginx/#header-manipulation

[github-actions]

Hi @shaun-nx thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!