You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kubectl get statefulset,svc,pods,pvc,pv --show-labels
159
+
echo "Waiting for broker to become active"
160
+
sleep 60; kubectl describe nodes
161
+
until kubectl get pods --show-labels | grep pubsubplus-0 | grep -m 1 -E '1/1'; do sleep 10; done
162
+
until kubectl get pods --show-labels | grep pubsubplus-1 | grep -m 1 -E '1/1'; do sleep 10; done
163
+
until kubectl get pods --show-labels | grep pubsubplus-2 | grep -m 1 -E '1/1'; do sleep 10; done
164
+
until kubectl get pods --show-labels | grep pubsubplus- | grep -m 1 -E 'active=true'; do sleep 10; done
165
+
bash -c 'if [[ `kubectl get po --show-labels | grep -c "1/1"` -ne 3 ]]; then echo "Some pods are not ready!"; kubectl get po --show-labels; exit 1; fi'
Copy file name to clipboardExpand all lines: docs/PubSubPlusK8SDeployment.md
+1-7
Original file line number
Diff line number
Diff line change
@@ -846,7 +846,7 @@ There are [multiple management tools](//docs.solace.com/Management-Tools.htm ) a
846
846
847
847
A random admin password will be generated if it has not been provided at deployment using the `solace.usernameAdminPassword` parameter, refer to the the information from `helm status` how to retrieve it.
848
848
849
-
**Important:** Every time `helm install`or `helm upgrade`is called a new admin password will be generated, which may break an existing deployment. Therefore ensure to always provide the password from the initial deployment as `solace.usernameAdminPassword=<PASSWORD>` parameter to subsequent `install` and `upgrade` commands.
849
+
**Important:** Every time `helm install` is called a new admin password will be generated. When reusing PVCs from a previous deployment, be cautious, as this action might generate a new password, potentially disrupting an existing deployment. Therefore, ensure to always provide the password from the initial deployment as `solace.usernameAdminPassword=<PASSWORD>` parameter to subsequent `install` commands.
850
850
851
851
#### WebUI, SolAdmin and SEMP access
852
852
@@ -1013,12 +1013,6 @@ solace:
1013
1013
redundancy: true
1014
1014
size: dev
1015
1015
```
1016
-
**Important:** this may not show, but be aware of an additional non-default parameter:
1017
-
```
1018
-
solace:
1019
-
usernameAdminPassword: jMzKoW39zz # The value is just an example
1020
-
```
1021
-
This has been generated at the initial deployment if not specified and must be used henceforth for all change requests, to keep the same. See related note in the [Admin Password section](#admin-password).
0 commit comments