https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
a
@fierce-summer-6167 this one
f
Do you know why you're seeing a 404 and not 503?
a
yes, because rke2 is "default" one directly listening on the 80,443 ports
f
What is the ingress type?
a
I installed two more controllers, traefik and apisix, but if I set Ingress with that class to some resource it's still nginx 404
so basically Ingress in this fashion has no effect
f
Ah. I meant the ingress service type.
a
I have NodePort mostly
f
If it's a NodePort, are you checking the NodePort? If it's a LoadBalancer, are you checking the load balancer endpoint?
a
even though I would prefer ClusterIP
f
ClusterIP is local to the cluster.
a
But currently I don't get it what I need to achieve this, or how this class is working
For me ingress is something like you have a reverse proxy and then it checks a class, and find the suitable service
f
It sounds like in your case that if you're trying to determine if the ingress is working correctly, you'll have to query the nodeport of the service.
Are you doing that, or ports 80/443? Are they the service ports for one of your ingresses?
a
I think rke2-ingress-nginx is doing the hostPort
## Use host ports 80 and 443 ## Disabled by default hostPort: # -- Enable 'hostPort' or not enabled: true ports: # -- 'hostPort' http port http: 80 # -- 'hostPort' https port https: 443
f
You're looking for something like: kubectl get services --namespace <ingress namespace>
a
So my question is... can I even achieve this ingress thing to be more configurable just within Kubernetes, and what steps/measures...
nginx isn't even in let's say exception admission clusterip
f
Yes, but I've never done it. We've deployed NGINX Ingress controller and Istio (for example, but Istio is not an ingress controller) on the same cluster, but not multiple ingresses. The Kubernetes project has some documentation here: https://kubernetes.github.io/ingress-nginx/user-guide/multiple-ingress/
Sounds like you were on the right track with ingress classes.
a
as a workaround I can use existing Ingress to forward traffic, but is manual job
Thank you for the input
36 Views
Open in Slack
PreviousNext
Powered by