Update README.md

chart/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: ucentralgw
-  repository: git+https://github.com/Telecominfraproject/wlan-cloud-ucentralgw@helm?ref=v2.1.0-RC2
+  repository: git+https://github.com/Telecominfraproject/wlan-cloud-ucentralgw@helm?ref=v2.1.0-RC3
   version: 0.1.0
 - name: ucentralsec
   repository: git+https://github.com/Telecominfraproject/wlan-cloud-ucentralsec@helm?ref=v2.1.0-RC1
@@ -17,5 +17,5 @@ dependencies:
 - name: kafka
   repository: https://charts.bitnami.com/bitnami
   version: 13.0.2
-digest: sha256:38927996b231cee0bab612414308e4b2931329c96634c15485bf7ff45413773f
-generated: "2021-09-02T12:35:25.840558653+03:00"
+digest: sha256:dd01079e0cd254744f00f3f85259ebd0c9893b965c9724819e40c4c912be20e4
+generated: "2021-09-08T13:12:25.763485669+03:00"

chart/Chart.yaml

@@ -2,10 +2,10 @@ apiVersion: v2
 name: wlan-cloud-ucentral
 appVersion: "1.0"
 description: A Helm chart for Kubernetes
-version: 2.1.0-RC2
+version: 2.1.0-RC3
 dependencies:
 - name: ucentralgw
-  repository: "git+https://github.com/Telecominfraproject/wlan-cloud-ucentralgw@helm?ref=v2.1.0-RC2"
+  repository: "git+https://github.com/Telecominfraproject/wlan-cloud-ucentralgw@helm?ref=v2.1.0-RC3"
   version: 0.1.0
 - name: ucentralsec
   repository: "git+https://github.com/Telecominfraproject/wlan-cloud-ucentralsec@helm?ref=v2.1.0-RC1"

docker-compose/.env

@@ -1,5 +1,5 @@
 COMPOSE_PROJECT_NAME=ucentral
-UCENTRALGW_TAG=v2.1.0-RC2
+UCENTRALGW_TAG=v2.1.0-RC3
 UCENTRALGWUI_TAG=v2.1.0-RC1
 UCENTRALSEC_TAG=v2.1.0-RC1
 UCENTRALFMS_TAG=v2.1.0-RC1

docker-compose/README.md

@@ -17,4 +17,6 @@ export FLAGS="-s --cacert <your-wlan-cloud-ucentral-deploy-location>/docker-comp
 ```
 The `--cacert` option is necessary since the REST API certificates are self-signed. Omit the option if you provide your own signed certificates.
 
+**Note**: When deploying with self-signed certificates you can not make use of the trace functionality in the UI since the AP will throw a TLS error when uploading the trace to uCentralGW. Please use the Letsencrypt deployment or provide your own valid certificates if you want to use this function.
+
 PS: The deployment creates local volumes to persist mostly application and database data. In addition to that several bind mounts are created: one for the `docker-compose/certs/` directory which is used by multiple services, and the other ones mount service specific data directories and configuration files located under `docker-compose/` into the appropriate containers. Be aware that for the bind mounts the host directories and files will be owned by the user in the container. Since the files are under version control, you may have to change the ownership to your user again before pulling changes.