FIPS 140-3 compliance
By offloading TLS termination to either Azure KeyVault Premium or Azure Managed HSM you can attain FIPS 140-3 level 3 compliance in your cluster ingress.
Secure Ingress with TLS Offload
A Kubernetes ingress with TLS offload using Azure Key Vault or Managed HSM
making your cluster FIPS 140-3 compliant
Key Features
TLS Offload
Move SSL/TLS termination out of your application pods and into the ingress controller. This reduces the overhead on your app while increasing the security in certificate management.
Seamless Migration
Drop-in replacement for ingress-nginx, with a familiar configuration and API.
Azure Key Vault or Managed HSM Integration
Securely fetch SSL/TLS certificates from Azure Key Vault or Managed HSM, without the need to store them in your cluster.
Flexible Configuration
Customize the ingress controller to your needs with support for annotations, ConfigMaps, and Helm charts.
High Availability
Deploy the ingress controller as a highly available Kubernetes Deployment with autoscaling capabilities.
