v1.3.7 Ingress-level Listener Port Support

What's Changed

• Added support for ingress-level listener port annotations by @piyush-tiwari in #73

Full Changelog: v1.3.6...v1.3.7

Release Notes

Currently, NIC creates a listener port on the IngressClass backed LB for each backend service port specified in the Ingress resource.

Users can now use the following annotations on their Ingress resources to specify a single listener LB port for all HTTP(S) communication. The values for these annotations should be numeric strings and they have no nil value, they should be removed entirely if not in use. :

oci-native-ingress.oraclecloud.com/http-listener-port: "80"
oci-native-ingress.oraclecloud.com/https-listener-port: "443"

Behaviour

• The port configured in oci-native-ingress.oraclecloud.com/http-listener-port will be used for all HTTP traffic handled by the LB for the Ingress. The routing policies will be configured accordingly, merging all rules specified in the Ingress resource.
• The port configured in oci-native-ingress.oraclecloud.com/https-listener-port will be used for all HTTPS traffic for TLS configured hosts by the LB for the Ingress. The routing policies will be configured accordingly, merging all rules specified in the Ingress resource. Note that if a Certificate Annotation is used in the Ingress resource, all hosts are considered TLS configured.