esteban1983cl
commented
3 years ago OK, I solved myself this issue adding the follow configuration in my values.yaml helm chart file. I pickup the configuration from https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.43.0/deploy/static/provider/aws/deploy-tls-termination.yaml
# Configures the ports the nginx-controller listens on
containerPort:
http: 80
https: 443
tohttps: 2443
---
config:
http-snipet: |
server {
listen 2443;
return 308 https://$host$request_uri;
}
---
service:
targetPorts:
# http: http
http: tohttps
https: http
aSapien
Nuru
stealthHat
fejta-bot
iamNoah1
baudlord
k8s-triage-robot
k8s-ci-robot
NGINX Ingress controller version: v0.43.0
Kubernetes version (use
kubectl version):Environment:
uname -a):What happened:
After upgrade helm chart from 3.12.0 to 3.22.0 I get this error message.
What you expected to happen:
The controller works fine.
How to reproduce it: Install helm chart using this values file:
values.yaml
```yaml ## nginx configuration ## Ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/index.md ## ## Overrides for generated resource names # See templates/_helpers.tpl # nameOverride: # fullnameOverride: controller: name: controller image: # I pulled from docker hub to my private repo. repository: registry.gitlab.com/xxxxxxxxxxxxxxx/nginx tag: "v0.43.0" digest: sha256:2b29d459bb978bc773fcfc824a837bb52d6223aba342411d22d61522e58f811b pullPolicy: IfNotPresent # www-data -> uid 101 runAsUser: 101 allowPrivilegeEscalation: true # Configures the ports the nginx-controller listens on containerPort: http: 80 https: 443 # Will add custom configuration options to Nginx https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/ config: "enable-real-ip": "true" "force-ssl-redirect": "true" "log-format-escape-json": "true" "log-format-upstream": "{ \"nginx.time\": \"$time_iso8601\", \"nginx.remote_addr\": \"$proxy_protocol_addr\", \"nginx.x-forward-for\": \"$proxy_add_x_forwarded_for\", \"nginx.request_id\": \"$req_id\", \"nginx.remote_user\": \"$remote_user\", \"nginx.bytes_sent\": $bytes_sent, \"nginx.request_time\": $request_time, \"nginx.status\": $status, \"nginx.vhost\": \"$host\", \"nginx.request_proto\": \"$server_protocol\", \"nginx.path\": \"$uri\", \"nginx.request_query\": \"$args\", \"nginx.request_length\": $request_length, \"nginx.duration\": $request_time, \"nginx.method\": \"$request_method\", \"nginx.http_referrer\": \"$http_referer\", \"nginx.http_user_agent\": \"$http_user_agent\", \"nginx.namespace\": \"$namespace\", \"nginx.ingress-name\": \"$ingress_name\", \"nginx.service-name\": \"$service_name\", \"nginx.service-port\": \"$service_port\", \"nginx.request_uri\": \"$request_uri\", \"nginx.scheme\": \"$scheme\", \"nginx.full_url\": \"$http_client_request_url\"}" "proxy-body-size": "50m" "proxy-connect-timeout": "1800" "proxy-read-timeout": "1800" "proxy-real-ip-cidr": "0.0.0.0/0" "proxy-send-timeout": "1800" "redirect-to-https": "true" "use-forwarded-headers": "true" "use-proxy-protocol": "false" "worker-rlimit-nofile": "102400" ## Annotations to be added to the controller config configuration configmap ## configAnnotations: {} # Will add custom headers before sending traffic to backends according to https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/customization/custom-headers proxySetHeaders: {} # Will add custom headers before sending response traffic to the client according to: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#add-headers addHeaders: {} # Optionally customize the pod dnsConfig. dnsConfig: "options": - "name": "dots" "value": "1" # Optionally change this to ClusterFirstWithHostNet in case you have 'hostNetwork: true'. # By default, while using host network, name resolution uses the host's DNS. If you wish nginx-controller # to keep resolving names inside the k8s network, use ClusterFirstWithHostNet. dnsPolicy: ClusterFirst # Bare-metal considerations via the host network https://kubernetes.github.io/ingress-nginx/deploy/baremetal/#via-the-host-network # Ingress status was blank because there is no Service exposing the NGINX Ingress controller in a configuration using the host network, the default --publish-service flag used in standard cloud setups does not apply reportNodeInternalIp: false # Required for use with CNI based kubernetes installations (such as ones set up by kubeadm), # since CNI and hostport don't mix yet. Can be deprecated once https://github.com/kubernetes/kubernetes/issues/23920 # is merged hostNetwork: false ## Use host ports 80 and 443 ## Disabled by default ## hostPort: enabled: false ports: http: 80 https: 443 ## Election ID to use for status update ## electionID: ingress-controller-leader-nginx-private ## Name of the ingress class to route through this controller ## ingressClass: nginx-http-private # labels to add to the pod container metadata podLabels: {} # key: value ## Security Context policies for controller pods ## podSecurityContext: {} ## See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for ## notes on enabling and using sysctls ### sysctls: {} # sysctls: # "net.core.somaxconn": "8192" ## Allows customization of the source of the IP address or FQDN to report ## in the ingress status field. By default, it reads the information provided ## by the service. If disable, the status field reports the IP address of the ## node or nodes where an ingress controller pod is running. publishService: enabled: true ## Allows overriding of the publish service to bind to ## Must beAnything else we need to know:
/kind bug