Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx not exposed anymore in the same way as before #5534

Closed
lgraziosi opened this issue Feb 27, 2024 · 2 comments
Closed

Nginx not exposed anymore in the same way as before #5534

lgraziosi opened this issue Feb 27, 2024 · 2 comments

Comments

@lgraziosi
Copy link

Hello, basically, we need to redirect the nginx ingress controller on another port, and we always used HAProxy to do that.
With the old v1.23.6+rke2r2 version we see this:

hostname:~ # ss -tapnu | grep :443
...
tcp      LISTEN       0          128                              [::]:443                                                  [::]:*                               users:(("nginx",pid=23404,fd=13),("nginx",pid=23392,fd=13))
tcp      LISTEN       0          128                              [::]:443                                                  [::]:*                               users:(("nginx",pid=23405,fd=21),("nginx",pid=23392,fd=21))

So we can do that without any issue.
With any newer version, that port is not seen anymore from the host, for example with a 1.23.16 version:

hostname:~ # ss -tapnu | grep :443
tcp      ESTAB        0         0                       redactedip:41458                                            10.43.0.1:443                            users:(("calico-node",pid=12648,fd=9))
tcp      ESTAB        0         0                       redactedip:41462                                            10.43.0.1:443                            users:(("flanneld",pid=12889,fd=7))
tcp      ESTAB        0         0                       redactedip:41460                                            10.43.0.1:443                            users:(("calico-node",pid=12647,fd=10))
hostname:~ # ss -tapnu | grep nginx
hostname:~ # 

So our haproxy can't redirect anymore to the port desired.

Do you guys have any idea about why nginx is not "exposed" anymore in the same way as before?
What changed? Is it parametrizable?
Thank you for your help.

@lgraziosi
Copy link
Author

Okay, after some tests, more specifically, when we upgrade from 1.23.7 to 1.23.8, the problem starts.

@brandond
Copy link
Member

brandond commented Feb 27, 2024

Kubernetes 1.23 has been end of maintenance for a year. The releases you are running, and upgrading to, are both well over a year old. Kubernetes 1.26 is end of maintenance tomorrow.

I suspect that the change you're seeing is related to #3129 - but again, you're on a very old version that we no longer support; I would recommend that you start moving on to much newer releases as soon as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants