Issue with EKS 1.26, ingress-controller (created using Helm)

[kcorelight]

What happened:

ingress-controller pod on EKS 1.26 is continuously restarting.

I have successfully deployed helm 4.0.6 on EKS 1.26.

When I try to move to helm 4.0.6 to 4.0.19, I see the following errors in pod logs

---

bytes.(*Buffer).ReadFrom(0xc00010e278, {0x1b7c180, 0xc0002023a8})
bytes/buffer.go:204 +0x98
crypto/tls.(*Conn).readFromUntil(0xc00010e000, {0x1b7e7a0, 0xc0000b4028}, 0x94d)
crypto/tls/conn.go:799 +0xe5
crypto/tls.(*Conn).readRecordOrCCS(0xc00010e000, 0x0)
crypto/tls/conn.go:606 +0x112
crypto/tls.(*Conn).readRecord(...)
crypto/tls/conn.go:574
crypto/tls.(*Conn).Read(0xc00010e000, {0xc000170000, 0x1000, 0x9a9c80})
crypto/tls/conn.go:1277 +0x16f
bufio.(*Reader).Read(0xc0003ae840, {0xc0002fa200, 0x9, 0x9b7c42})
bufio/bufio.go:227 +0x1b4
io.ReadAtLeast({0x1b7bfe0, 0xc0003ae840}, {0xc0002fa200, 0x9, 0x9}, 0x9)
io/io.go:328 +0x9a
io.ReadFull(...)
io/io.go:347
golang.org/x/net/http2.readFrameHeader({0xc0002fa200, 0x9, 0xc00142c060}, {0x1b7bfe0, 0xc0003ae840})
golang.org/x/[email protected]/http2/frame.go:237 +0x6e
golang.org/x/net/http2.(*Framer).ReadFrame(0xc0002fa1c0)
golang.org/x/[email protected]/http2/frame.go:498 +0x95
golang.org/x/net/http2.(*clientConnReadLoop).run(0xc0001bff98)
golang.org/x/[email protected]/http2/transport.go:2101 +0x130
golang.org/x/net/http2.(*ClientConn).readLoop(0xc00003ca80)
golang.org/x/[email protected]/http2/transport.go:1997 +0x6f
created by golang.org/x/net/http2.(*Transport).newClientConn
golang.org/x/[email protected]/http2/transport.go:725 +0xac5

What you expected to happen:

Above error is being seen on ingress-controller pod

Ingress-controller is not coming up on EKS 1.26

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):

Ingress controller version : 1.0.5

Kubernetes version (use kubectl version):

1.26

Environment:

AWS EKS

• How was the ingress-nginx-controller installed:

Using helm_release (terraform provider)

• Current State of the controller:
  kumar@kumars-MBP invest-infra % kubectl describe ingressclasses
  Name: nginx
  Labels: app.kubernetes.io/component=controller
  app.kubernetes.io/instance=ingress-nginx
  app.kubernetes.io/managed-by=Helm
  app.kubernetes.io/name=ingress-nginx
  app.kubernetes.io/version=1.0.5
  helm.sh/chart=ingress-nginx-4.0.9
  Annotations: meta.helm.sh/release-name: ingress-nginx
  meta.helm.sh/release-namespace: ingress-nginx
  Controller: k8s.io/ingress-nginx
  Events:
  kumar@kumars-MBP invest-infra %

• Current state of ingress object, if applicable:

nginx

• Others:
  • Any other related information like ;
    • copy/paste of the snippet (if applicable)
    • kubectl describe ... of any custom configmap(s) created and in use
    • Any other related information that may help

How to reproduce this issue:

Deplo helm nginx controller verion 4.0.9 -
https://github.com/kubernetes/ingress-nginx/releases?page=7

Anything else we need to know:

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/remove-kind bug

Install on EKS as per documentation here https://kubernetes.github.io/ingress-nginx/deploy/#aws

[longwuyuan]

• Please reopen if required
• If you reopen, then kindly edit the issue descripion as per hints below
  • click the new bug report button in a new browser tab and look at the questions asked
  • then edit the issue description here and answer those questions

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

• Please reopen if required
• If you reopen, then kindly edit the issue descripion as per hints below
• click the new bug report button in a new browser tab and look at the questions asked
• then edit the issue description here and answer those questions

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.