在部署或升级之前,需要参考官方提供的版本支持说明。一般而言尽量使用最新版本,官方明确说明所有版本是生产可用的,并且可实现稳定升级,不会存在版本回退的兼容性问题。
在镜像选择方面,支持基于Alpine、Debian、Redhat-Ubi 三种基础进行构建的镜像。并且还提供 OpenTracing 链路跟踪模块的版本,具体如下:
Name | Base image | Third-party modules | DockerHub image | Architectures | |
---|---|---|---|---|---|
Alpine-based image | nginx:1.21.6-alpine, which is based on alpine:3.15 | nginx/nginx-ingress:2.2.0-alpine | arm/v7, arm64, amd64, ppc64le, s390x | ||
Alpine-based image with OpenTracing | nginx:1.21.6-alpine, which is based on alpine:3.15 | NGINX OpenTracing module, OpenTracing library, OpenTracing tracers for Jaeger, Zipkin and Datadog | nginx/nginx-ingress:2.2.0-alpine-ot | arm/v7, arm64, amd64, ppc64le, s390x | |
Debian-based image | nginx:1.21.6, which is based on debian:bullseye-slim | nginx/nginx-ingress:2.2.0 | arm/v7, arm64, amd64, ppc64le, s390x | ||
Debian-based image with OpenTracing | nginx:1.21.6, which is based on debian:bullseye-slim | NGINX OpenTracing module, OpenTracing library, OpenTracing tracers for Jaeger, Zipkin and Datadog | nginx/nginx-ingress:2.2.0-ot | arm/v7, arm64, amd64, ppc64le, s390x | |
Ubi-based image | redhat/ubi8 | nginx/nginx-ingress:2.2.0-ubi | arm64, amd64, s390x |
Nginx官方提供三种部署方式:
● 清单文件部署:虽然繁琐,但是自定义更加方便。由于Nginx部署方便,我更倾向于直接使用清单文件部署。
● Chart 部署:方便后续的管理
● Operator 部署:目前 starts 少,不推荐使用