Welcome! Log In Create A New Profile

Advanced

nginxStatusAllowCidr

June 06, 2023 11:16AM
When updating nginx controller in our k8s environment using helm command we see the vaules is being updated but the pod nginx.conf is not showing allowed cidr.

Helm command used:
helm upgrade -i nginx-ingress . --namespace nginx-ingress -f internal-ingress.yaml --set controller.replicaCount=2 --set controller.nodeSelector."kubernetes\.io/os"=linux --set defaultBackend.nodeSelector."kubernetes\.io/os"=linux --set controller.service.externalTrafficPolicy=Local --set controller.image.repository=AZUREREPO/ingress-nginx/controller --set defaultBackend.image.registry=AZUREREPO/ingress-nginx --set controller.service.loadBalancerIP=X.X.X.X --set controller.service.enabled=true --set controller.nginxStatus.allowCidrs="X.X.X.0/23"

pod nginx.conf:
stub_status only showing allow 127.0.0.1

snippet of values which were found using helm get values -a:
nginxStatus:
allowCidrs: 192.168.132.0/23
enable: true

Anyone have experience setting allowCidrs?
Subject Author Posted

nginxStatusAllowCidr

ptrane55@gmail.com June 06, 2023 11:16AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 152
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready