nginx

Announcing NGINX Ingress Controller for Kubernetes Release 1.5.0 h4 { font-weight:bolder; font-size:110%; } h5 { font-weight:bolder; font-size:110%; } We are pleased to announce release 1.5.0 of the NGINX Ingress Controller for Kubernetes. This represents a milestone in the development of our supported solution for Ingress load balancing on Kubernetes platforms, including Amazon Elastic Container Service for Kubernetes (EKS), the Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE), Red Hat OpenShift, IBM Cloud Private, Diamanti, and others. Release 1.5.0 includes: A new configuration approach using NGINX custom resources to easily define ingress policies Additional metrics, provided by a streamlined Prometheus exporter Simplified configuration of complex TLS deployments Support for load balancing traffic to external services, using ExternalName services A dedicated Helm chart repository The complete changelog for release 1.5.0, including bug fixes, improvements, and changes, is available in our GitHub repo. What Is the NGINX Ingress Controller for [ more… ]

Validating OAuth 2.0 Access Tokens with NGINX and NGINX Plus Image courtesy of John T. on unsplash.com There are many options for authenticating API calls, from X.509 client certificates to HTTP Basic authentication. In recent years, however, a de facto standard has emerged in the form of OAuth 2.0 access tokens. These are authentication credentials passed from client to API server, and typically carried as an HTTP header. OAuth 2.0, however, is a maze of interconnecting standards. The processes for issuing, presenting, and validating an OAuth 2.0 authentication flow often rely on several related standards. At the time of writing there are eight OAuth 2.0 standards, and access tokens are a case in point, as the OAuth 2.0 core specification (RFC 6749) does not specify a format for access tokens. In the real world, there are two formats in common usage: JSON Web Token (JWT) as [ more… ]

NGINX Is Now Officially Part of F5 Today it’s official: NGINX is now part of F5. When F5 announced its intention to acquire NGINX, I wrote about how one chapter of the NGINX story was ending and the next beginning. In the almost two months since then, members of the F5 and NGINX teams have been planning how the companies will come together. All the hard work pays off today as we officially start executing our plans and authoring the new chapter together. My colleague, Sidney Rabsatt, will talk in an upcoming blog about the value of merging our respective technologies. In this post, I want to focus on the value of merging the people, culture, and vision of the two companies. Let me start by reassuring everyone of a few things: NGINX is becoming a business unit within F5. We [ more… ]

NGINX Controller API Management Module vs. Kong: Performance Comparison table.nginx-blog, table.nginx-blog th, table.nginx-blog td { border: 2px solid black; border-collapse: collapse; } table.nginx-blog { width: 100%; } table.nginx-blog th { background-color: #d3d3d3; align: left; padding-left: 5px; padding-right: 5px; padding-bottom: 2px; padding-top: 2px; line-height: 120%; } table.nginx-blog td { padding-left: 5px; padding-right: 5px; padding-bottom: 2px; padding-top: 5px; line-height: 120%; } table.nginx-blog td.center { text-align: center; padding-bottom: 2px; padding-top: 5px; line-height: 120%; } h4 { font-weight:bolder; font-size:110%; } h5 { font-weight:bolder; font-size:110%; } The API management (APIM) market is a crowded space. The latest Gartner Magic Quadrant for Full Life Cycle API Management ranks 22 vendors, with 7 in the Leaders quadrant. Competing in an existing market requires establishing a strong position to differentiate and stand out from the competition. So what makes NGINX’s API management solution different? At NGINX our goal is to make [ more… ]