Skip to content

Commit 0379e1e

Browse files
committed
chore(release): v2.0.2
1 parent d143943 commit 0379e1e

File tree

2 files changed

+18
-36
lines changed

2 files changed

+18
-36
lines changed

community-solid-server/Chart.yaml

+1-3
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ type: application
1515
# This is the chart version. This version number should be incremented each time you make changes
1616
# to the chart and its templates, including the app version.
1717
# Versions are expected to follow Semantic Versioning (https://semver.org/)
18-
version: 2.0.1
18+
version: 2.0.2
1919

2020
# This is the version number of the application being deployed. This version number should be
2121
# incremented each time you make changes to the application. Versions are not expected to
@@ -33,5 +33,3 @@ maintainers:
3333
name: jveessen
3434
sources:
3535
- https://github.com/solid/community-server
36-
37-

community-solid-server/README.md

+17-33
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,27 @@
11
# Deploying Community Solid Server
2+
23
## TL;DR
3-
```
4+
5+
```bash
46
helm repo add community-solid-server https://communitysolidserver.github.io/css-helm-chart/charts/
57
helm install my-css community-solid-server/community-solid-server
68
```
9+
710
## Introduction
11+
812
This chart bootstraps a [Community Solid Server](https://github.com/CommunitySolidServer/CommunitySolidServer) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
913

1014
## Prerequisites
15+
1116
- Kubernetes 1.19+
1217
- Helm 3.2.0+
1318
- PV provisioner support in the underlying infrastructure if you want to use Persistence functionality.
1419

1520
## Installing the Chart
21+
1622
To install the chart with the release name my-css:
1723

18-
```
24+
```bash
1925
helm repo add idlab-gent https://communitysolidserver.github.io/css-helm-chart/charts/
2026
helm install my-css community-solid-server/community-solid-server
2127
```
@@ -25,9 +31,10 @@ These commands deploy Community Solid Server on the Kubernetes cluster in the de
2531
> Tip: List all releases using `helm list`
2632
2733
## Uninstalling the Chart
34+
2835
To uninstall/delete the my-css deployment:
2936

30-
```
37+
```bash
3138
helm delete my-css
3239
```
3340

@@ -45,15 +52,13 @@ The command removes all the Kubernetes components associated with the chart and
4552
| `image.pullPolicy` | CSS image pull policy | `IfNotPresent` |
4653
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
4754

48-
4955
### Common parameters
5056

5157
| Name | Description | Value |
5258
| ------------------ | ----------------------------------------- | ----- |
5359
| `nameOverride` | String to partially override css.fullname | `""` |
5460
| `fullnameOverride` | String to fully override css.fullname | `""` |
5561

56-
5762
### Community Solid Server parameters
5863

5964
| Name | Description | Value |
@@ -67,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
6772
| `baseUrlOverride` | From the helm config, an appropriate --baseUrl value will be passed to the community server. If however you wish to override this set this parameter appropriately. | `""` |
6873
| `customParameters` | An array of `flag` `value` pairs to be added to the CSS cli command for custom parameters/overwrites. | `[]` |
6974

70-
7175
### Persistence parameters
7276

7377
| Name | Description | Value |
@@ -79,7 +83,6 @@ The command removes all the Kubernetes components associated with the chart and
7983
| `persistence.size` | CSS persistent volume size | `128Mi` |
8084
| `persistence.selector` | Selector to match an existing Persistent Volume | `{}` |
8185

82-
8386
### Kubernetes Service parameters
8487

8588
| Name | Description | Value |
@@ -88,7 +91,6 @@ The command removes all the Kubernetes components associated with the chart and
8891
| `service.port` | CSS Kubernetes service port | `80` |
8992
| `service.nodePort` | CSS Kubernetes service node port, only relevant when service.type == `NodePort` | `""` |
9093

91-
9294
### Ingress resource parameters
9395

9496
| Name | Description | Value |
@@ -98,8 +100,7 @@ The command removes all the Kubernetes components associated with the chart and
98100
| `ingress.path` | Default path for the ingress resource | `/` |
99101
| `ingress.annotations` | Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations. | `{}` |
100102
| `ingress.tls` | TLS Configuration | `[]` |
101-
| `ingress.className` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) | `""` |
102-
103+
| `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) | `""` |
103104

104105
### Infrastructure parameters
105106

@@ -114,33 +115,12 @@ The command removes all the Kubernetes components associated with the chart and
114115
| `tolerations` | Tolerations for pod assignment | `[]` |
115116
| `affinity` | Affinity for pod assignment | `{}` |
116117

117-
118-
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
119-
```
120-
helm install my-css \
121-
--set config.bundled=file \
122-
idlab-gent/css
123-
```
124-
The above command deploys Community Solid Server with the bundled `file` config.
125-
126-
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
127-
128-
```
129-
helm install my-css -f values.yaml idlab-gent/css
130-
```
131-
> Tip: You can use the default values.yaml
132-
133-
You can even mix these two modes to override values from your YAML file with the `--set` argument. For example,
134-
135-
```
136-
helm install my-css -f values.yaml --set config.bundled=file idlab-gent/css
137-
```
138-
> This can be useful when trying out config changes or to enable debug logging for temporarily.
139-
140118
# Configuration and Installation details
141119

142120
## Using a bundled config
121+
143122
To use any of the bundled configs of CSS, specify which config to use by overriding `config.bundled` with any of the following values:
123+
144124
- default (default)
145125
- dynamic
146126
- example-https-file
@@ -154,19 +134,23 @@ To use any of the bundled configs of CSS, specify which config to use by overrid
154134
- sparql-file-storage
155135

156136
## Using a custom config
137+
157138
To use a custom config, the `config.configMapName` and `config.configMapKey` variables are used.
158139

159140
First create a configmap resource to hold your config on the cluster. For example when you have a json file called `my-config.json`:
141+
160142
```
161143
kubectl create configmap my-configmap --from-file my-config.json
162144
```
163145

164146
Alternatively when you have multiple configs in a directory called `my-configs`, you can bundle a whole directory into one configmap like so:
147+
165148
```
166149
kubectl create configmap my-configmap --from-file my-configs/
167150
```
168151

169152
Then override this name and key values accordingly (key of the config will be the same as the filename), for example:
153+
170154
```yaml
171155
config:
172156
configMapName: my-configmap

0 commit comments

Comments
 (0)