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