Using NIC 4.0 with server-snippets, location-snippets, http-snippets. Can I upgrade NIC to 5.x?

Projects NGINX Ingress Controller
1

My issue: About to upgrade NIC 4.0 to 5.0 . But as per official documentation, open tracing is removed and it affects users using server-snippets/location-snippets. We are using snippets to map variables for CORS usage. Is it safe to deploy 5.x to production ?

“With the removal of the OpenTracing dynamic module from NGINX Plus R34, NGINX Ingress Controller also removes full OpenTracing support. This will affect users making use of OpenTracing with the ConfigMap, server-snippets & location-snippets parameters. Support for tracing with OpenTelemetry will come in a future release.“

Version of NIC and/or NGINX: ( Open source. Not Nginx Plus ) 4.0.1-alpine. 1.27.4 nginx

Deployment environment: Dev, Prod

2

If you were not using OpenTracing, your update to 5.X.X should be straightforward. We do not recommend deploying directly in production without testing. When you use snippets, you use them at your own risk; we do not validate their content, meaning they can break in production.

The safest approach would be Blue-Green deployment.

2 Likes
3

If you’re not using OpenTracing, upgrading NIC to 5.x should be pretty smooth just be cautious when using snippets, as they’re not validated and could break things. The safest route is a blue–green deployment for testing before full rollout.

2 Likes