found an error (#58)

* found an error

README.md

@@ -1,11 +1,11 @@
 # wlan-cloud-helm
 This repository contains helm charts for various deployment types of the tip wlan cloud services.
 
-# IMPORTANT - CloudSDK Helm charts v0.4 to v1.x migration procedure
+# IMPORTANT - Cloud Controller Helm charts v0.4 to v1.x migration procedure
 
-We've introduced breaking changes to how CloudSDK database charts are managed.
-If you want to preserve your data when moving from v0.4 to v1.x of the CloudSDK Helm charts, follow the steps outlined below.
-If you can re-install your CloudSDK and don't care to loose your data, you can skip the steps and just install the upstream charts version with no changes to the default installation procedure.
+We've introduced breaking changes to how Cloud Controller database charts are managed.
+If you want to preserve your data when moving from v0.4 to v1.x of the Cloud Controller Helm charts, follow the steps outlined below.
+If you can re-install your Cloud Controller and don't care to loose your data, you can skip the steps and just install the upstream charts version with no changes to the default installation procedure.
 
 ## Prerequisites
 
@@ -148,7 +148,7 @@ minikube start --memory=10g --cpus=4 --driver=virtualbox --extra-config=kubelet.
 
 Please note that you may choose another driver (parallels, vmwarefusion, hyperkit, vmware, docker, podman) which might be more suitable for your setup. Omitting this option enables auto discovery of available drivers.
 
-Deploy CloudSDK chart:
+Deploy Cloud Controller chart:
 
 ```
 helm upgrade --install tip-wlan tip-wlan -f tip-wlan/resources/environments/dev-local.yaml -n default

tip-wlan/charts/wlan-integrated-cloud-component-service/templates/deployment.yaml

@@ -25,10 +25,11 @@ spec:
         {{- toYaml .Values.podSecurityContext | nindent 8 }}
       {{- if .Values.integratedWithPersistence.enabled }}
       initContainers:
-        - name: {{ include "common.name" . }}-readiness
-          image: busybox:1.28
-          imagePullPolicy: {{ .Values.pullPolicy | default .Values.global.pullPolicy }}
-          command: ['sh', '-c', "until nslookup {{ $pg }}.{{ $ns }}.svc.cluster.local; do echo waiting for POSTGRES; sleep 2; done"]
+      - name: wait-for-services
+        image: opsfleet/depends-on:latest
+        args:
+        - "-service={{ .Release.Name }}-postgresql"
+        - -check_interval=5
       - name: {{ include "common.name" . }}-create-db-schema
         env:
         - name: POSTGRESQL_PORT_NUMBER
@@ -61,10 +62,6 @@ spec:
           echo "***** Now executing cloud-sdk-schema-postgresql.sql and creating/updating schema on Postgres instance *****"
           PGPASSWORD=$POSTGRES_PASSWORD psql -h {{- include "postgresql.service" . -}} -U postgres -f cloud-sdk-schema-postgresql.sql
           exit
-          ports:
-          - containerPort: 5432
-            name: tcp-postgresql
-            protocol: TCP
         resources:
           requests:
             cpu: 50m
@@ -157,7 +154,7 @@ spec:
       volumes:
       - name: certificates
         secret:
-          secretName: {{ include "common.fullname" . }}-certs
+          secretName: tip-common-postgres-client-certs
       - name: logback-config
         configMap:
             name: {{ include "common.fullname" . }}-log-config

tip-wlan/resources/certs/README.md

@@ -1,2 +1,2 @@
-Contains certs needed for this service to start.
+Contains certs needed for cloud controller to work
 Please refer to page: https://telecominfraproject.atlassian.net/wiki/spaces/WIFI/pages/262176803/Pre-requisites+before+deploying+Tip-Wlan+solution