move policy config to onap 1.1

was the cause of the robot failure for policy in oom

Issue-ID: OOM-297

Change-Id: Iabb24cc7a007ef852cde3ebe2cbb9226bb4153b3
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Signed-off-by: Ahmed Alabulrahman <ahmed.alabdulrahman@amdocs.com>
diff --git a/kubernetes/policy/values.yaml b/kubernetes/policy/values.yaml
index 1b2ed0f..62e91f8 100644
--- a/kubernetes/policy/values.yaml
+++ b/kubernetes/policy/values.yaml
@@ -4,12 +4,12 @@
 image:
   readiness: oomk8s/readiness-check
   readinessVersion: 1.0.0
-  policyPe: nexus3.onap.org:10001/openecomp/policy/policy-pe
+  policyPe: nexus3.onap.org:10001/onap/policy/policy-pe
   policyPeVersion: 1.1-STAGING-latest
-  policyDrools: nexus3.onap.org:10001/openecomp/policy/policy-drools
+  policyDrools: nexus3.onap.org:10001/onap/policy/policy-drools
   policyDroolsVersion: 1.1-STAGING-latest
-  policyDb: nexus3.onap.org:10001/openecomp/policy/policy-db
+  policyDb: nexus3.onap.org:10001/onap/policy/policy-db
   policyDbVersion: 1.1-STAGING-latest
-  policyNexus: nexus3.onap.org:10001/openecomp/policy/policy-nexus
+  policyNexus: nexus3.onap.org:10001/onap/policy/policy-nexus
   policyNexusVersion: 1.1-STAGING-latest
   ubuntu: ubuntu:16.04