quaint-rose-98687
11/19/2022, 2:19 AMmicroscopic-diamond-94749
11/19/2022, 7:19 AMquaint-rose-98687
11/20/2022, 7:09 PMmicroscopic-diamond-94749
11/21/2022, 8:44 AMexternal
cloud provider and ingress.provider: none
and then installed openstack cloud provider manager and ingress-nginx afterwardsingress-nginx
service of Type Loadbalancer
was provisioned and I could install rancher with a refular ingress option.quaint-rose-98687
11/22/2022, 10:57 AMmicroscopic-diamond-94749
11/22/2022, 11:41 AMservice
do you use? Nodeport
?$ kubectl get svc -n cattle-system rancher
give as output?quaint-rose-98687
11/22/2022, 11:54 AMroot@rancher-fsn1:~# kubectl get svc -n cattle-system rancher
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
rancher ClusterIP 10.43.165.105 <none> 80/TCP,443/TCP 4d3h
microscopic-diamond-94749
11/22/2022, 12:23 PMkubectl get ns |grep ingress
?quaint-rose-98687
11/22/2022, 7:36 PMroot@rancher-fsn1:~# kubectl get ns |grep ingress
ingress-nginx Active 4d11h
microscopic-diamond-94749
11/23/2022, 9:34 AMingress-nginx
configured? k get svc -n ingress-nginx
and is the ingress created k get ingress -A
?quaint-rose-98687
11/23/2022, 3:35 PMNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx-controller-admission ClusterIP 10.43.125.241 <none> 443/TCP 5d7h
NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE
cattle-system cm-acme-http-solver-kv9mr <none> <http://myclusterdomain.com|myclusterdomain.com> 65.108.208.205,78.47.146.214,78.47.182.83 80 4d13h
cattle-system rancher nginx <http://myclusterdomain.com|myclusterdomain.com> 65.108.208.205,78.47.146.214,78.47.182.83 80, 443 5d6h
rancher-cluster.yml
from https://docs.ranchermanager.rancher.io/how-to-guides/new-user-guides/kubernetes-cluster-setup/rke1-for-ranchermicroscopic-diamond-94749
11/24/2022, 8:57 AMingress-nginx
installed, but without a service? Is it a DaemonSet
with hostports? Then you can just point your loadbalancer to all three nodes, port 80 & 443.quaint-rose-98687
11/25/2022, 8:15 AMmicroscopic-diamond-94749
11/26/2022, 2:17 PMk get pod,ds,deploy -n ingress-nginx
shows you the pod, daemonsets and deployments in the namespace _ingress-nginx`. I'm not surprised it gives you a 404, the ingress controller listens on the host
in the ingress resource.