https://wiki.onap.org/display/DW/ONAP+on+Kubernetes?focusedCommentId=22250653#comment-22250653

Good question, I guess we live with port mapping requiring the vnc-portal so we can run multiple environments on the same host each with 30xxx, 31xxx etc.. but in reality most of us by default run one set of ONAP containers.  Myself when I work in postman I use the 30xxx ports except for using the SDC gui - in the vnc-portal. 

I think we need a JIRA to run ONAP in affective single port mapping config where 8989 for example maps to 8989 outside the namespace and not 30211 - for ease of development.

Andrew Fenner

Hi,

I'm new to Kubernates and to OOM but so the following question could have a obvious answer that I've completely missed.

Is there a reason not to use the following commands to expose the K8s containers so that you don't have to log on via the VNC sever which is just a pain.

kubectl expose services portalapps --type=LoadBalancer --port 8989 --target-port=8080 --name=frontend -n onap-portal
kubectl expose services sdc-fe --type=LoadBalancer --port 8181 --target-port=8181 --name=frontend -n onap-sdc
kubectl expose services vid-server --type=LoadBalancer --port 8080 --target-port=8080 --name=frontend -n onap-vid

This exposed the portal, Vid and SDC so then the K8S services could be used directly. Then the ip address to use can just be found using 

kubectl get services -all-namespaces=true | grep -i frontend or you can assign the IP address using -external-ip=w.x.y.z

Then I just updated the hosts file as "normal"

Thanks

/Andrew