# Nodeport/proxy/loadbalancer **URL:** \ **Category:** SUSE Rancher Prime\ **Created:** [January 15, 2021, 3:36am UTC](https://forums.suse.com/t/nodeport-proxy-loadbalancer/19291 "2021-01-15T03:36:34Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![vprocopan](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vprocopan/32/7095_2.png) [@vprocopan](https://forums.suse.com/u/vprocopan)\ **Post date:** [January 15, 2021, 3:36am UTC](https://forums.suse.com/t/nodeport-proxy-loadbalancer/19291/1 "2021-01-15T03:36:34Z")
Hello! After installing rancher it said that I am supposed to access it via the loadbalancer. The question is how do I make it accessible externally from another IP? Here is my kubectl get all > [vprocopan@ctmasternode ~]$ kubectl get all > NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE > service/kubernetes ClusterIP 10.43.0.1 443/TCP 13h > [vprocopan@ctmasternode ~]$ kubectl get all --all-namespaces > NAMESPACE NAME READY STATUS RESTARTS AGE > cattle-system pod/rancher-54dfc89757-2pqsr 1/1 Running 0 13h > cattle-system pod/rancher-54dfc89757-xjqdd 1/1 Running 1 13h > cattle-system pod/rancher-54dfc89757-xpv9v 1/1 Running 0 13h > cattle-system pod/rancher-webhook-5c6fcb875-l8fsp 1/1 Running 0 13h > fleet-system pod/fleet-agent-7d959597cb-zkx2r 1/1 Running 0 12h > fleet-system pod/fleet-controller-78c4566f5f-bblvn 1/1 Running 0 12h > fleet-system pod/gitjob-55cd477bdd-qpqmt 1/1 Running 0 12h > ingress-nginx pod/default-http-backend-67cf578fc4-99dc7 1/1 Running 0 13h > ingress-nginx pod/nginx-ingress-controller-hghwk 1/1 Running 0 13h > ingress-nginx pod/nginx-ingress-controller-qx248 1/1 Running 0 13h > kube-system pod/canal-dv97n 2/2 Running 0 13h > kube-system pod/canal-lv7f2 2/2 Running 0 13h > kube-system pod/canal-n62mt 2/2 Running 0 13h > kube-system pod/coredns-7c5566588d-58w7g 1/1 Running 0 13h > kube-system pod/coredns-7c5566588d-s97wl 1/1 Running 0 13h > kube-system pod/coredns-autoscaler-65bfc8d47d-9fn5n 1/1 Running 0 13h > kube-system pod/metrics-server-6b55c64f86-v475r 1/1 Running 0 13h > kube-system pod/rke-coredns-addon-deploy-job-264hh 0/1 Completed 0 13h > kube-system pod/rke-ingress-controller-deploy-job-hm5b8 0/1 Completed 0 13h > kube-system pod/rke-metrics-addon-deploy-job-vdsdv 0/1 Completed 0 13h > kube-system pod/rke-network-plugin-deploy-job-jvs6q 0/1 Completed 0 13h > rancher-operator-system pod/rancher-operator-57f5cd9bc4-bcpd6 1/1 Running 0 13h > > NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE > cattle-system service/rancher ClusterIP 10.43.94.31 80/TCP,443/TCP 13h > cattle-system service/rancher-webhook ClusterIP 10.43.157.193 443/TCP 13h > default service/kubernetes ClusterIP 10.43.0.1 443/TCP 13h > fleet-system service/gitjob ClusterIP 10.43.145.58 80/TCP 13h > ingress-nginx service/default-http-backend ClusterIP 10.43.74.228 80/TCP 13h > kube-system service/kube-dns ClusterIP 10.43.0.10 53/UDP,53/TCP,9153/TCP 13h > kube-system service/metrics-server ClusterIP 10.43.94.195 443/TCP 13h > > NAMESPACE NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE > ingress-nginx daemonset.apps/nginx-ingress-controller 2 2 2 2 2 13h > kube-system daemonset.apps/canal 3 3 3 3 3 [kubernetes.io/os=linux](http://kubernetes.io/os=linux) 13h > > NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE > cattle-system deployment.apps/rancher 3/3 3 3 13h > cattle-system deployment.apps/rancher-webhook 1/1 1 1 13h > fleet-system deployment.apps/fleet-agent 1/1 1 1 13h > fleet-system deployment.apps/fleet-controller 1/1 1 1 13h > fleet-system deployment.apps/gitjob 1/1 1 1 13h > ingress-nginx deployment.apps/default-http-backend 1/1 1 1 13h > kube-system deployment.apps/coredns 2/2 2 2 13h > kube-system deployment.apps/coredns-autoscaler 1/1 1 1 13h > kube-system deployment.apps/metrics-server 1/1 1 1 13h > rancher-operator-system deployment.apps/rancher-operator 1/1 1 1 13h > > NAMESPACE NAME DESIRED CURRENT READY AGE > cattle-system replicaset.apps/rancher-54dfc89757 3 3 3 13h > cattle-system replicaset.apps/rancher-webhook-5c6fcb875 1 1 1 13h > fleet-system replicaset.apps/fleet-agent-6d98ff6fb5 0 0 0 13h > fleet-system replicaset.apps/fleet-agent-79b88948f9 0 0 0 13h > fleet-system replicaset.apps/fleet-agent-7d959597cb 1 1 1 12h > fleet-system replicaset.apps/fleet-controller-568dc5cdf4 0 0 0 13h > fleet-system replicaset.apps/fleet-controller-78c4566f5f 1 1 1 12h > fleet-system replicaset.apps/gitjob-55cd477bdd 1 1 1 12h > fleet-system replicaset.apps/gitjob-5bbbbbc6fb 0 0 0 13h > ingress-nginx replicaset.apps/default-http-backend-67cf578fc4 1 1 1 13h > kube-system replicaset.apps/coredns-7c5566588d 2 2 2 13h > kube-system replicaset.apps/coredns-autoscaler-65bfc8d47d 1 1 1 13h > kube-system replicaset.apps/metrics-server-6b55c64f86 1 1 1 13h > rancher-operator-system replicaset.apps/rancher-operator-57f5cd9bc4 1 1 1 13h > > NAMESPACE NAME COMPLETIONS DURATION AGE > kube-system job.batch/rke-coredns-addon-deploy-job 1/1 2s 13h > kube-system job.batch/rke-ingress-controller-deploy-job 1/1 2s 13h > kube-system job.batch/rke-metrics-addon-deploy-job 1/1 2s 13h > kube-system job.batch/rke-network-plugin-deploy-job 1/1 2s 13h ---
**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\ **Post date:** [January 15, 2021, 11:40am UTC](https://forums.suse.com/t/nodeport-proxy-loadbalancer/19291/2 "2021-01-15T11:40:49Z")
This is explained on [Rancher Docs: Set up Infrastructure for a High Availability RKE Kubernetes Cluster](https://rancher.com/docs/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/infra-for-ha/)