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

Issue with ingress #1

Open
getkub opened this issue Feb 3, 2024 · 6 comments
Open

Issue with ingress #1

getkub opened this issue Feb 3, 2024 · 6 comments

Comments

@getkub
Copy link

getkub commented Feb 3, 2024

Not able to work with the ingress

kubectl apply -f ingress/nginx-ingress-n8n-service.yml
The Service "nginx-ingress-n8n" is invalid: spec.ports[0].nodePort: Invalid value: 5678: provided port is not in the valid range. The range of valid ports is 30000-32767
@sysadmin-info
Copy link
Owner

sysadmin-info commented Feb 4, 2024 via email

@byteshiva
Copy link

Here you have a solution https://sysadmin.info.pl/en/blog/nginx-ingress-controller-for-n8n-how-to-create-it-and-deploy-in-kubernetes/

sob., 3 lut 2024, 17:37 użytkownik getkub @.***> napisał:

Not able to work with the ingress kubectl apply -f ingress/nginx-ingress-n8n-service.yml The Service "nginx-ingress-n8n" is invalid: spec.ports[0].nodePort: Invalid value: 5678: provided port is not in the valid range. The range of valid ports is 30000-

How can we achieve the same thing for Talos Linux?

"Also you need to modify the k3s service to change port range the way I presented. Without this it will not work, just because I am using a NodePort 5678 and by default Kubernetes is using a range for ports between 30000 and 32767. "

Refer:
https://www.talos.dev/v1.6/talos-guides/network/ingress-firewall/

@sysadmin-info
Copy link
Owner

sysadmin-info commented Apr 1, 2024 via email

@byteshiva
Copy link

byteshiva commented Apr 1, 2024

You need to modify the range of ports for k3s service. I presented how to do it. niedz., 31 mar 2024, 07:28 użytkownik Siva @.***> napisał:

I'm not using k3s; instead, I'm utilizing Talos Linux. Additionally, with Talos Linux, I don't have access to SSH.

@byteshiva
Copy link

You need to modify the range of ports for k3s service. I presented how to do it. niedz., 31 mar 2024, 07:28 użytkownik Siva @.***> napisał:

I'm not using k3s; instead, I'm utilizing Talos Linux. Additionally, with Talos Linux, I don't have access to SSH.

I received a reply from Talos stating that it's not a Talos issue but rather lacks Kubernetes best practices.

siderolabs/talos#8513 (comment)

@sysadmin-info
Copy link
Owner

You need to modify the range of ports for k3s service. I presented how to do it. niedz., 31 mar 2024, 07:28 użytkownik Siva @.***> napisał:

I'm not using k3s; instead, I'm utilizing Talos Linux. Additionally, with Talos Linux, I don't have access to SSH.

I received a reply from Talos stating that it's not a Talos issue but rather lacks Kubernetes best practices.

siderolabs/talos#8513 (comment)

I created a tutorial for k3s cluster not for Talos. So if you are using Talos, try to find out is it possible to modify the range. Or stay with the standard port instead modifying the service change the port from 5678 to 30000. Just 5678 is a default port for n8n and the problem is that the Kubernetes best practices are using by default this range: 30000 and 32767. So, f it says that the port is wrong, and you cannot modify the service in Talos (I do not know this) just modify the port in file nginx-ingress-n8n-service.yml as I wrote and implement the yaml file using the below command:
kubectl apply -f ingress/nginx-ingress-n8n-service.yml
What I did, I modified the port against Kubernetes best practices, to show that it is possible. Is it secure? Yes, but only if you work with the environment you can secure by isolating it from the Internet and also by isolating it using VLANs inside your network.

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

3 participants