Dive deep into two Linux features that underlie containers: namespaces and cgroups. They enable process isolation, ensuring that multiple processes running on a system don't interfere with one another. Our NGINX Unit application server also uses them for application isolation.
NGINX Service Mesh Release 1.1.0 introduces three key enhancements that make it easier to deploy and manage our production-ready service mesh in Kubernetes: Helm support, air-gap installation, and in-place upgrades.
If services in a Kubernetes environment exchange sensitive data, it's important to control communication among them. With NGINX Service Mesh, it takes less than 10 minutes to set up fine‑grained control. Watch the video demo and check out our step-by-step tutorial.
Traffic splitting is a valuable tool for app development, reducing the risk of outages during app upgrades. With NGINX Service Mesh, it takes less than 10 minutes to implement blue-green and canary deployments. Watch the video demo and check out our step-by-step tutorials.
Microservices March is a month-long virtual festival of microservices activities here at NGINX. Whether you’re already using Kubernetes in production or your interest is just blossoming, you’re sure to find sessions to pique your interest. Check out the schedule on our blog!
We explain how production-grade Kubernetes solves the challenges of deploying containerized microservices-based apps, which include culture, complexity, and security. In addition to a Kubernetes infrastructure you need a scalable Ingress controller, WAF, and service mesh.
NGINX Ingress Controller now supports single sign-on with OpenID Connect. Release 1.10.0 also introduces new configuration queue metrics, annotations on log entries, better validation of annotations and secrets, support for NGINX App Protect user-defined signatures, and more.
We provide guidance on where to deploy application services in a Kubernetes environment, using WAF as an example. Depending on your needs, it can make sense to deploy your WAF at the "front door" of the environment, on the Ingress Controller, per-service, or per-Pod.
We explain why duplicating application services paradoxically can improve overall efficiency: because NetOps and DevOps teams have different mandates, it makes sense for them to select and manage the tools that best suit their specific needs.