Brian, As part of the fix, it is now required for user of a k8s cluster to put the external ip of their nodes in the dcaegen2/values.yaml (https://github.com/onap/oom/blob/amsterdam/kubernetes/dcaegen2/values.yaml#L11-L19 <https://github.com/onap/oom/blob/amsterdam/kubernetes/dcaegen2/values.yaml#L11-L19>) file, as explained here: https://github.com/onap/oom/blob/amsterdam/kubernetes/config/onap-parameters-sample.yaml#L4-L8 <https://github.com/onap/oom/blob/amsterdam/kubernetes/config/onap-parameters-sample.yaml#L4-L8>
The reason for that is we need to expose the reverse proxy service on all the nodes, so the UEB port is open everywhere. kube-proxy will manage to route the traffic to the node having the nginx service. Hope it helps. I know this change is not convenient, but it was the only good/easy was for Amsterdam. This fix will be revisit in Beijing. Thanks, Alexis > On Feb 12, 2018, at 5:25 PM, FREEMAN, BRIAN D <[email protected]> wrote: > > > Trying to bring up OOM in Azure with the latest rancher/heml recommended and > SDC and others cant seem to get to UEB. > > https://jira.onap.org/browse/OOM-654 <https://jira.onap.org/browse/OOM-654> > mentions that the external IP has to be open on UEB port but I don’t see that > in my kube portal. > Only the 10.42 address is open on port 3904. > > Is there something I need to check or change in the rancher GUI ? > > Brian > > > > _______________________________________________ > onap-discuss mailing list > [email protected] <mailto:[email protected]> > https://lists.onap.org/mailman/listinfo/onap-discuss > <https://lists.onap.org/mailman/listinfo/onap-discuss>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
