...
What happens when the portal-app chart is deployed is that a K8s service is created that instantiates a load balancer. The LB chooses the private interface of one of the nodes (if happening in a multi-node K8S cluster deployment) as in the example below (i.e. in OpenStack, 10.0.0.4 is the private to IP of the specific K8s cluster node VM only). Then, to be able to access the portal on port 8989 from outside theK K8s & Openstack environmentthe OpenStack private network where the K8S cluster is connected to, the user needs to assign/get the specific floating IP address that corresponds to the private IPof the K8S Node VM where the Portal Service (as shown below) is deployed at.
| No Format |
|---|
kubectl -n onap get services|grep "portal-app" portal-app LoadBalancer 10.43.142.201 10.0.0.4 8989:30215/TCP,8006:30213/TCP,8010:30214/TCP 1d app=portal-app,release=dev |
...
In this example, that public floating IP is 10.12.56.155 which can be obtained through the horizon GUI or the Openstack CLI for your tenant (openstack server list) . That IP is then used in your /etc/hosts to map the fixed DNS aliases required by the ONAP Portal as shown below.
...