This week I tried to install and use the current rancher/rancher:stable (which is the same as rancher/rancher:latest). On my "old" Rancher setup which I created two years ago, I had
18.09 docker
rancher1.13.4-rancher1-1
rancher server
v2.1.7
Everything is running on Hetzner Cloud.
What kind of request is this (question/bug/enhancement/feature request):
Question
Question: How to use Ingress (at Hetzner Cloud)
Steps to reproduce (least amount of steps as possible):
Create a Rancher instance rancher/rancher:stable
Not sure if this also happening on other platforms too
This week I tried to install and use the current
rancher/rancher:stable
(which is the same asrancher/rancher:latest
). On my "old" Rancher setup which I created two years ago, I hadEverything is running on Hetzner Cloud.
What kind of request is this (question/bug/enhancement/feature request):
Question
Question: How to use Ingress (at Hetzner Cloud)
Steps to reproduce (least amount of steps as possible):
rancher/rancher:stable
https://github.com/mxschmitt/ui-driver-hetzner
TD/RLI can see that there are new options added in "v2.5.8" compared to my old Rancher (v2.1.7) (like ingress)
nginx
orrancher/hello-world
with two podsNodePort
(it is reachable, of course)ClusterIP
workload
(I also triedservice
)Do I have to check/uncheck something (like "Nginx Ingres" or "Nginx Default Backend") to get the Ingress working?
Result:
nginx.default.MY_IP.xip.io
address is not reachable:DNS_PROBE_POSSIBLE
Expected Result:
show
nginx
orrancher/hello-world
page in browserEnvironment information
rancher/rancher
/rancher/server
image tag or shown bottom left in the UI):v2.5.8 all current / unchanged settings
Cluster information
kubectl version
):docker version
):20.10.7