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
@@ -166,29 +166,7 @@ After applying the Helmfile, you can verify the deployment by listing the Helm r
166
166
helm list
167
167
```
168
168
169
-
# Appendix A - Cluster Role Configuration
170
-
171
-
## In case a data plane deployed twice or more on the same K8S cluster
172
-
173
-
### Edit the following parameter `rbacClusterWide` in the environment section of the helmfile.yaml file
174
-
```yaml
175
-
environments:
176
-
default:
177
-
values:
178
-
- ./environments/default.yaml
179
-
- rbacCreate: true
180
-
- rbacClusterWide: true
181
-
```
182
-
183
-
### Update `telegraf` Cluster Role Binding with the additional namespace. Add the following to the `subjects` section. (edit namespace variable)
184
-
```yaml
185
-
subjects:
186
-
- kind: ServiceAccount
187
-
name: telegraf
188
-
namespace: superstream-new-namespace
189
-
```
190
-
191
-
# Appendix B - Non-HA Deployment
169
+
# Appendix A - Non-HA Deployment
192
170
193
171
## For testing purposes only Superstream can be deployed without HA capabilities
194
172
@@ -201,9 +179,9 @@ environments:
201
179
- haDeployment: false
202
180
```
203
181
204
-
# Appendix C - Superstream Update
182
+
# Appendix B - Superstream Update
205
183
206
-
## Minor update
184
+
## Minor update - X.X.1 -> X.X.2
207
185
208
186
### To update the Superstream Data Plane version, run the following steps.
209
187
@@ -222,7 +200,7 @@ environments:
222
200
helmfile -e default apply
223
201
```
224
202
225
-
## Major update
203
+
## Major update - X.1.X -> X.2.X
226
204
227
205
### The first step involves backing up your current `default.yaml` file. Following this, update your repository by pulling the latest changes from the master branch. Once updated, merge your backup values into the environments/default.yaml file. Continue with the process by following these instructions:
228
206
@@ -253,7 +231,7 @@ helmfile -e default diff
253
231
helmfile -e default apply
254
232
```
255
233
256
-
# Appendix D - Uninstall
234
+
# Appendix C - Uninstall
257
235
258
236
## Steps to Uninstall Superstream Data Plane Deployment.
259
237
@@ -269,3 +247,114 @@ It's crucial to delete the stateful storage linked to the data plane. Ensure you
Copy file name to clipboardExpand all lines: environments/default.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
helmVersion: 0.1.10# Define the version of the superstream helm chart.
1
+
helmVersion: 0.2.1# Define the version of the superstream helm chart.
2
2
namespace: superstream # Specify the Kubernetes namespace where the resources will be deployed, isolating them within this designated namespace.
3
3
name: <DATAPLANE_NAME> # Define the data plane name within 32 characters, excluding '.', and using only letters, numbers, '-', and '_'.
4
4
accountId: ""# Provide the account ID that is associated with the deployment, which could be used for identifying resources or configurations tied to a specific account.
0 commit comments