Skip to content

Commit

Permalink
helm install from oci
Browse files Browse the repository at this point in the history
  • Loading branch information
Philip Stadermann committed Jan 16, 2024
1 parent 46e0db1 commit 1d8ea57
Showing 1 changed file with 6 additions and 14 deletions.
20 changes: 6 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,10 @@ Vaas helm is a chart for deploying Verdict-as-a-Service on-premise.

1. Create a minimal values.yaml file:

The token has to be set in the `global.secret.dockerconfigjson` and `gdscan.secret.dockerconfigjson` variable on deployment.
To access the VaaS docker containers, the image pull secret has to be set in the `global.secret.dockerconfigjson` and `gdscan.secret.dockerconfigjson` variable.

`values`-File for a minimum example deployment:

`values`-File for a minimum example deployment.
```yaml
global:
imagePullSecrets:
Expand All @@ -21,25 +22,16 @@ gdscan:
dockerconfigjson: "$$_BASE64_ENCODED_JSON_CONTAINING_TOKEN_$$"
```
Copy the `secret.yaml` you got from G DATA to the template folder.

2. Add the helm repository:

```bash
helm repo add vaas https://gdatasoftwareag.github.io/vaas/
```

3. Install Verdict-as-a-Service:
2. Install Verdict-as-a-Service:
```bash
helm install vaas gdatasoftware/vaas -f values.yaml
helm install vaas oci://ghcr.io/gdatasoftwareag/charts/vaas -f values.yaml -n vaas
```

### Updating Verdict-as-a-Service

```bash
helm repo update
helm upgrade vaas gdatasoftware/vaas -f values.yaml
helm upgrade vaas oci://ghcr.io/gdatasoftwareag/charts/vaas -f values.yaml -n vaas
```

# Verdict-as-a-Service on-premise
Expand Down

0 comments on commit 1d8ea57

Please sign in to comment.