synching up portal config again
PORTAL-130 renamed various mounts and FQDNs
-it also added an additional logback.xml for portalsdk
What I did was move the 2 logback files into the config/log dir
so that the centralized logging team can update them as required.
Was able to login to the portal using the vnc session
Issue-ID: OOM-340
Change-Id: Id1872422e7d876953ecb0a92ce55a8753d9d7eaa
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
diff --git a/kubernetes/portal/values.yaml b/kubernetes/portal/values.yaml
index eadc834..a5edb98 100644
--- a/kubernetes/portal/values.yaml
+++ b/kubernetes/portal/values.yaml
@@ -3,10 +3,10 @@
nodePortPrefix: 302
image:
readiness: oomk8s/readiness-check:1.0.0
- portalapps: nexus3.onap.org:10001/openecomp/portal-apps:1.3-STAGING-latest
- portaldb: nexus3.onap.org:10001/openecomp/portal-db:1.3-STAGING-latest
+ portalapps: nexus3.onap.org:10001/onap/portal-apps:1.3-STAGING-latest
+ portaldb: nexus3.onap.org:10001/onap/portal-db:1.3-STAGING-latest
mariadbClient: oomk8s/mariadb-client-init:1.0.0
- portalwms: nexus3.onap.org:10001/openecomp/portal-wms:1.3-STAGING-latest
+ portalwms: nexus3.onap.org:10001/onap/portal-wms:1.3-STAGING-latest
ubuntuInit: oomk8s/ubuntu-init:1.0.0
ubuntuDesktop: dorowu/ubuntu-desktop-lxde-vnc
filebeat: docker.elastic.co/beats/filebeat:5.5.0