-
Bug
-
Resolution: Done
-
High
-
None
-
None
-
None
Portal application assumes that its client (typically VNC container) has certain entries in /etc/hosts file that map host name alias to appropriate kubernetes service IP. E.g.:
10.111.126.71 sdc.api.be.simpledemo.onap.org
10.103.44.19 portal.api.simpledemo.onap.org
10.110.95.76 policy.api.simpledemo.onap.org
10.108.34.73 sdc.api.simpledemo.onap.org
10.107.166.182 vid.api.simpledemo.onap.org
10.107.100.231 aai.api.simpledemo.onap.org
Currently the entries are added to the /etc/hosts file using init-container.
However, the IPs can change (e.g. service redeployed) or kubernetes can rewrite /etc/hosts file as this is managed by kubernetes.
- is blocked by
-
LOG-333 OOM vnc-portal container down since 20171114:2300UTC after helm upgrade from 2.3 to 2.6 and Rancher 1.6.11 on same day
- Closed
- is cloned by
-
OOM-546 Provide option to collect ONAP env details for issue investigations
- Closed
-
OOM-467 Optimize config-init process
- Closed
- relates to
-
PORTAL-212 Portal URL and VNC Container
- Closed