v1.3.9 Bugfix release

What's Changed

• Sync with Internal Repo for bug fixes by @piyush-tiwari in #83
  -- Fixed a bug where Native Ingress Controller panics if no TLS configuration is supplied for HTTP2 annotated ingresses
  -- Fixed Issue #78, where LB BackenSets weren't getting created for Ingresses which referenced services with named TargetPort, in clusters with Native Pod Networking as the CNI
• Bump protobuf and net dependencies by @piyush-tiwari in #84

Full Changelog: v1.3.8...v1.3.9

v1.3.8 TCP Listener Support

What's Changed

• Extract CA chain from tls.crt if ca.crt is missing for secret-type tls artifact by @antoniolago and @piyush-tiwari in #76
• Add TCP listener support by @piyush-tiwari in #81

Full Changelog: v1.3.7...v1.3.8

New features and support

• For HTTPS/TLS support, you can now supply the entire certificate chain in tls.crt field and omit the ca.crt field in the sample configuration. Expected order is server certificate first, and then the certificate authority chain.
• TCP Listeners are supported now, sample Ingress available at TCP Listener Support.

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.

v1.3.6 Bugfix release

What's Changed

• Update default cni for get cluster calls by @Inbaraj-S in #72

Full Changelog: v1.3.5...v1.3.6

v1.3.5 Bugfix release

What's Changed

• Add metadata env variable by @piyush-tiwari in #67
• Fix namespace deletion on helm upgrade by @piyush-tiwari in #68

New Contributors

• @piyush-tiwari made their first contribution in #67

Full Changelog: v1.3.4...v1.3.5

v1.3.4 Bugfix Release

What's Changed

• oke-30296-fix-multi-nodeport-bug by @Inbaraj-S in #52
• Added missing namespace check during install by @matthewmcdaniel in #55
• Specify region in values.yaml during deployment.yaml by @matthewmcdaniel in #53

PS: In this release we have found a issue in the chart where the namespace may get deleted if user tries to upgrade after installing the 1.3.4 chart version. You will be impacted if you have taken the latest chart from this release and try to run subsequent upgrade of helm. If you are already working under this release please move to 1.3.5 before any helm upgrade.

New Contributors

• @matthewmcdaniel made their first contribution in #55

Full Changelog: v1.3.3...v1.3.4

v1.3.3 SSL Termination at LB

What's Changed

• Add support to disable TLS on the backend via the new annotation oci-native-ingress.oraclecloud.com/backend-tls-enabled: "false".
• Release doc update v1.3.3 by @Inbaraj-S in #50

New Contributors

• @robo-cap made their first contribution in #44

Full Changelog: v1.3.2...v1.3.3

V1.3.2 Multi arch support

Updates

• Added support for Multi-Arch-Manifest images(ARM and AMD).

• Bugfix:

  • Ingress state build failure due to missing ingressclass definition. #33

Multi-Arch Image Test Release

• Sanity test for ARM/AMD support.

V1.3.0

Support for flannel

You can now set up the OCI native ingress controller to load balance and route incoming traffic to pods running on worker nodes in a Kubernetes cluster that is using the flannel CNI plugin for pod networking. Previously, you could only set up the OCI native ingress controller when the cluster was using the OCI VCN-Native Pod Networking CNI plugin for pod networking.

Native Ingress Controller will be using the externalTrafficPolicy mentioned in the service detail to determine the worker node addition strategy to the LB Backendset.

In simple terms:
Local - Add only the worker nodes which have pods deployed to them.
Cluster - Add all the worker nodes to the backendset.

Changes

• OKE-27032 Flannel Support by @Inbaraj-S in #28

Full Changelog: v1.2.0...v1.3.0