Apart from debugging, there shouldn't be any need to access Consul from
outside the cluster, so it doesn't expose a NodePort service.
When I need debugging access, I use kubernetes port-forwarding. For
example, from a machine that has access to the cluster, I do:
kubectl -n onap port-forward svc/consul-server-ui 8500:8500
Then, from the same machine, I use localhost:8500 to access Consul.
--- Jack
On 1/28/21 12:06 PM, Kenneth Lehner wrote:
I was expecting to see NodePort for Consul:
kubectl -n onap get services | grep consul
consul ExternalName consul-server.onap.svc.cluster.local 43h
consul-serverClusterIPNone8301/TCP 43h
consul-server-ui ClusterIP170.1.212.134 8500/TCP 43h
msb-consul ClusterIP170.1.201.828500/TCP 43h
What is the URL/port for accessing Consul's UI in this configuration?
What other information do I need to get the IP and port?
If I go to http://40.112.55.96:30270/ui/
<http://40.112.55.96:30270/ui/> I get "refused to connect" (that IP is
the address in the /etc/hosts file).
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22774): https://lists.onap.org/g/onap-discuss/message/22774
Mute This Topic: https://lists.onap.org/mt/80188303/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
