Skip to content

Commit c7ac1e0

Browse files
committed
helm deployment remove not needed variables
Signed-off-by: Thomas Telleis <[email protected]>
1 parent bf9aa0e commit c7ac1e0

File tree

1 file changed

+11
-14
lines changed
  • docs/deploy-and-configure/installation/scenario-k8s-deployment

1 file changed

+11
-14
lines changed

docs/deploy-and-configure/installation/scenario-k8s-deployment/index.md

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,7 @@ kubectl create secret docker-registry eccenca-docker-registry-credentials \
262262
--docker-server=https://docker-registry.eccenca.com \
263263
--docker-username=<your-docker-username> \
264264
--docker-password=<your-docker-password> \
265-
--namespace <your-namespace>
265+
--namespace cmem
266266
```
267267
Replace the placeholders with the provided registry details and credentials.
268268

@@ -275,16 +275,16 @@ If you have a dedicated license file, create a secret with a `license.asc` data
275275
```console
276276
kubectl create secret generic cmem-license \
277277
--from-file license.asc
278-
--namespace <your-namespace>
278+
--namespace cmem
279279
```
280280

281281
Then, add the secret name to your `values.yaml` file for the key `global.license`.
282282

283283
For more background on license, see also: https://documentation.eccenca.com/latest/deploy-and-configure/configuration/dataplatform/application-full/
284284

285-
### 3. Configure your deployment
285+
### 3. Create a `cmem-values.yaml` file
286286

287-
Create a file named `cmem-values.yaml` to configure your Corporate Memory deployment.
287+
To configure your Corporate Memory deployment create a file named `cmem-values.yaml`.
288288
At a minimum, you should configure the
289289
- `hostname`, under which the deployment is reachable later
290290
- `cmemClientSecret`, if you use the postgres provisioning dump the default is fine
@@ -351,19 +351,16 @@ Use `helm` to deploy the chart.
351351

352352
```console
353353
# In case you have the chart or repostiory locally available
354-
helm upgrade --install <release-name> .
355-
--namespace <your-namespace> \
354+
helm upgrade --install cmem .
355+
--namespace cmem \
356356
-f my-values.yaml
357357
358358
# or use our helm repository
359-
helm upgrade --install <release-name> cmem-helm/cmem
360-
--namespace <your-namespace> \
359+
helm upgrade --install cmem cmem-helm/cmem
360+
--namespace cmem \
361361
-f my-values.yaml
362362
```
363363

364-
- `<release-name>`: A name for this release (e.g., `cmem`).
365-
- `<your-namespace>`: The namespace created in step 2.
366-
367364
This command will install the chart in the specified namespace using your custom configuration.
368365

369366
_See [configuration](#configuration) below for more details on available options._
@@ -375,12 +372,12 @@ _See [helm install](https://helm.sh/docs/helm/helm_install/) for command documen
375372
After the installation is complete, you can check the status of the pods:
376373

377374
```console
378-
kubectl get pods --namespace <your-namespace>
375+
kubectl get pods --namespace cmem
379376
```
380377

381378
You can also check the rollout status of the StatefulSets:
382379

383380
```console
384-
kubectl rollout status statefulset/explore --namespace <your-namespace>
385-
kubectl rollout status statefulset/dataintegration --namespace <your-namespace>
381+
kubectl rollout status statefulset/explore --namespace cmem
382+
kubectl rollout status statefulset/dataintegration --namespace cmem
386383
```

0 commit comments

Comments
 (0)