产品动态
公告
产品发布记录
values.yaml 配置方法:controller:extraInitContainers:- name: sysctlimage: busyboximagePullPolicy: IfNotPresentsecurityContext:privileged: truecommand:- sh- -c- |sysctl -w net.core.somaxconn=65535 # 调大链接队列,防止队列溢出sysctl -w net.ipv4.ip_local_port_range="1024 65535" # 扩大源端口范围,防止端口耗尽sysctl -w net.ipv4.tcp_tw_reuse=1 # TIME_WAIT 复用,避免端口耗尽后无法新建连接sysctl -w fs.file-max=1048576 # 调大文件句柄数,防止连接过多导致文件句柄耗尽config:# nginx 与 client 保持的一个长连接能处理的请求数量,默认100,高并发场景建议调高,但过高也可能导致 nginx ingress 扩容后负载不均。# 参考: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#keep-alive-requestskeep-alive-requests: "1000"# nginx 与 upstream 保持长连接的最大空闲连接数 (不是最大连接数),默认 320,在高并发下场景下调大,避免频繁建联导致 TIME_WAIT 飙升。# 参考: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#upstream-keepalive-connectionsupstream-keepalive-connections: "2000"# 每个 worker 进程可以打开的最大连接数,默认 16384。# 参考: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#max-worker-connectionsmax-worker-connections: "65536"
values.yaml 配置方法:controller:config:# nginx 日志落盘到日志文件,避免高并发下占用过多 CPUaccess-log-path: /var/log/nginx/nginx_access.logerror-log-path: /var/log/nginx/nginx_error.logextraVolumes:- name: log # controller 挂载日志目录emptyDir: {}extraVolumeMounts:- name: log # logratote 与 controller 共享日志目录mountPath: /var/log/nginxextraContainers: # logrotate sidecar 容器,用于轮转日志- name: logrotateimage: imroc/logrotate:latest # https://github.com/imroc/docker-logrotateimagePullPolicy: IfNotPresentenv:- name: LOGROTATE_FILE_PATTERN # 轮转的日志文件 pattern,与 nginx 配置的日志文件路径相匹配value: "/var/log/nginx/nginx_*.log"- name: LOGROTATE_FILESIZE # 日志文件超过多大后轮转value: "100M"- name: LOGROTATE_FILENUM # 每个日志文件轮转的数量value: "3"- name: CRON_EXPR # logrotate 周期性运行的 crontab 表达式,这里每分钟一次value: "*/1 * * * *"- name: CROND_LOGLEVEL # crond 日志级别,0~8,越小越详细value: "8"volumeMounts:- name: logmountPath: /var/log/nginx
文档反馈