From e3a2b6fed94e2caab5f9f2424beace6e4cea0013 Mon Sep 17 00:00:00 2001 From: dave kormann Date: Thu, 14 Nov 2019 23:30:43 -0500 Subject: [PATCH] FIX: Correct default image name in nanobot values.yaml nanobot's values.yaml was pointing to a private repo and incorrect tag for its default image. This change fixes that, along with choosing a more appropriate repo secret name. signed-off-by: dave kormann Change-Id: I72b0d9f9d4e08224817e4ea71aa9df9a3f2967f8 --- ric_robot_suite/helm/nanobot/values.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ric_robot_suite/helm/nanobot/values.yaml b/ric_robot_suite/helm/nanobot/values.yaml index 16ac5a6..353f069 100644 --- a/ric_robot_suite/helm/nanobot/values.yaml +++ b/ric_robot_suite/helm/nanobot/values.yaml @@ -27,9 +27,9 @@ images: name: alpine # tag: latest run: - repository: snapshot.docker.ranco-dev-tools.eastus.cloudapp.azure.com:10001 - name: test/nanobot - tag: latest + repository: nexus3.o-ran-sc.org:10004 + name: o-ran-sc/it-test-nanobot + tag: 0.0.1 # note: the helm chart does not create repository credential secrets. # If your repository requires authentication, create a docker-registry # secret with @@ -39,7 +39,7 @@ images: # and fill in secret-name below. Only one secret should be created per # registry. The chart will take care of producing a unique list of # imagePullSecrets. - repositoryCred: azure-secret + repositoryCred: o-ran-registry-secret ric: cluster: # The kubernetes cluster name. To find this, do: -- 2.16.6