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

V1.2.0

This is a bugfix release v1.2.0 of OCI Native Ingress Controller.

Release Notes

BugFix

This release fixes the duplicate LB creation via network and timeout errors post the default retry attempts.

V1.1.0

This is an minor release v1.1.0 of OCI Native Ingress Controller.

Release Notes

Support for Web Application Firewalll Integration

• Annotation oci-native-ingress.oraclecloud.com/waf-policy-ocid which enables user to add firewall policy id to IngressClass. It helps us create and add firewall to the corresponding LB.

Support for enabling LB shape updates

• Enables dynamic shape updates on LB via ingressclassparameters. Eg: maxBandwidthMbps: 400, minBandwidthMbps: 100

Added resource tags for LB resource created via ingress controller

• Added resource tag for LB created via ingress controller : oci-native-ingress-controller-resource: loadbalancer

Bugfix & Others

• Fixed multi-path routing bug
• Readme document updated.
• Updated Kubernetes Supported Version - v1.26.2.

Contributors: @nirpai @Inbaraj-S

v1.0.0

This release is the first GA release 1.0.0 of OCI Native Ingress Controller for Kubernetes.

Release notes

Principal support

• Support for configuring native ingress controller with using User or Instance principals for performing OCI operations.

Host based routing

• Ability to route requests that match a particular host to a configured service backend. Ex Requests that match “foo.bar.com” should go to service “foo”.
• Support for hostname wildcards like “*.bar.com”

Path based routing

• Ability to route requests that match a particular URI to a configured service backend. Ex Requests with the URI that starts with /serviceA should go to service A.

Default backend support

• Ability to deploy a default backend to respond in case the request parameters does not match with any of the configured paths.

Ingress Class Support

• Ability to map an ingress resource to native ingress controller in case there are other ingress controllers running in the cluster.

Secured Communication (HTTPS)

• Ability to use Kubernetes secrets with TLS certificates to secure ingress routes.
• Ability to use OCI Certificate service certificates to secure ingress routes.

Pod Readiness Gate

• Support for Pod readiness Gates to achieve zero downtime rolling deployments.

Support for Managed and Virtual Nodes

• Support for Kubernetes clusters with Managed and Virtual node type node pools. The Virtual node type node pools are only supported with User principal configuration.

Monitoring and Metrics

• Support for adding custom metrics for controller.

Not Supported

• Flannel based Kubernetes clusters.
• Configuring native ingress controller with ‘Workload’ Identity principal type.

Contributors: @nirpai @Inbaraj-S @vbhargav875

Test release v0.0.2

Testing complete setup before release.

Test release 0.0.1

• Testing complete build docker workflow.

Contributors: @Inbaraj-S @nirpai