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
This chart will provision volsync backupd and restore manifests.
45
+
This is to centralize the otherwise repeated backupd and restore manifests, from being ludicrously repetitive.
46
+
This chart aims to have reasonable defaults to reduce the amount of customization required.
47
+
This chart does not provision the volsync CRDs, this is left to the user, who must install the volsync operator and CRDs.
48
+
This chart also does not provision the restic secrets, which necessarily must be generated by the end user.
49
+
50
+
These manifests will automatically restore from a backupd on volume creation. This means that when a volume is deleted the contents will be restored from the backupd.
51
+
This chart makes use of volsyncs volume populator, which sources new volumes from a backupd on volume creation to restore from backupd.
52
+
53
+
## Changelog
54
+
55
+
### 0.7.0
56
+
57
+
This minor patch introduced backwards compatible restore changes. This included being able to select the previous integer, and asOf date so users can select which backup to restore.
58
+
59
+
No changes are necessary to the values.yaml but if you would like to use the new restore options you need to add `.restore.asOf` or `.restore.previous`. Note this are not populated by the base chart and they should be used mutually exclusively.
This release adds previously missing inbuilt startup probe configuration.
115
+
This is backwards compatible since no changes to values.yaml and it does not change the default behaviour.
116
+
117
+
To add a startup probe you can add the following to your values.yaml for the most basic startup probe:
118
+
119
+
```yaml
120
+
startupProbe:
121
+
httpGet:
122
+
path: /
123
+
port: http # the port name if it is not call http
124
+
```
125
+
126
+
### 0.7.0
127
+
128
+
This release introduces a daemonset template. This is backwards compatible since no changes to values.yaml. If you would like to use this new template you can do something akin to the following. Replace ``corvid-test`` with your charts name:
129
+
130
+
```yaml
131
+
{{- define "corvid-test.daemonset" }}
132
+
# your daemonset overrides here
133
+
{{- end }}
134
+
{{- include "corvid.daemonset" (list . "corvid-test.daemonset") }}
135
+
```
136
+
137
+
### 0.6.5
138
+
139
+
This release introduces existingClaim persistence for the podSpec template. Thus this effects almost all usages, but only if ``.persistence.existingClaim`` is set.
140
+
141
+
By default please add the following to your values.yaml, although this is not required:
142
+
143
+
```yaml
144
+
persistence:
145
+
existingClaim: ""
146
+
```
147
+
148
+
No changes are required in the templating itself, this is backwards compatible.
149
+
150
+
### 0.6.4
151
+
152
+
This release of corvid introduces CronJob templates. This is backwards compatible since the only new variables are part of a new template altogether to define a CronJob.
153
+
Any users seeking to invoke this new CronJob will need to add the following to their values.yaml:
154
+
155
+
```yaml
156
+
schedule: "@midnight"# or some other cron schedule, try: https://crontab.guru/
157
+
```
158
+
159
+
They will also need to invoke this new template in their templates (substituting ``corvid-test`` for their chart name):
160
+
161
+
```yaml
162
+
{{- define "corvid-test.cronjob" -}}
163
+
# your cronjob overrides here
164
+
{{- end -}}
165
+
{{- include "corvid.cronjob" (list . "corvid-test.cronjob") -}}
This chart is a chart which contains multiple other more atomic charts as dependencies.
8
+
This allows you to control a broader deployment of interconnected resources.
9
+
10
+
In this instance this is a meta chart for jellyfin, with components like metube and filebrowser to help automate and remotely administer the jellyfin data files. This is because jellyfin currently has no in-built video downloader, and thus we need tools like metube and filebrowser to help.
11
+
7
12
## Installing the Chart
8
13
9
14
To install the chart with the release name `jellymeta`, run the following commands:
Copy file name to clipboardexpand all lines: charts/qbittorrent/CHANGELOG.md
-99
Original file line number
Diff line number
Diff line change
@@ -1,102 +1,3 @@
1
-
# qBittorrent Helm Chart
2
-
3
-
This helm chart is used to deploy qBittorrent into a kubernetes cluster.
4
-
This uses mostly standard values you will also find in other charts like those of bitnami.
5
-
6
-
This chart specifically has optional support for gluetun running as a side-car. See the initContainers section of the values.yaml for specific configuration to enable this. This will only require that you create your own secret to provide environment variables to gluetun. Please ensure you bind your qBittorrent in advanced options to only the tunnel interface. In my case this was tun0. Then also use ipleaks ``torrent address detection`` to ensure you are maintaining privacy. Also consider enabling qBittorrents anonymous mode.
7
-
8
-
This chart makes heavy use of my own corvid library chart, to reduce the amount of boilerplate I have to maintain across my charts.
9
-
10
-
More details are to come, please consult the values.yaml for specifics.
11
-
12
-
## Usage
13
-
14
-
### Example Values
15
-
16
-
To create a qbittorrent client with your VPN you can use the following values as a rough guide. You will need to change the storage, and the host to match your own needs. You will also need to bring your own secret. In the following configuration I use the ``gluetun`` secret. This will be mounted with every key as environment variables to configure your gluetun setup. See https://github.com/qdm12/gluetun-wiki/tree/main/setup/providers for environment variables you will need to add to this secret.
This helm chart is used to deploy qBittorrent into a kubernetes cluster.
2
+
This uses mostly standard values you will also find in other charts like those of bitnami.
3
+
4
+
This chart specifically has optional support for gluetun running as a side-car. See the initContainers section of the values.yaml for specific configuration to enable this. This will only require that you create your own secret to provide environment variables to gluetun. Please ensure you bind your qBittorrent in advanced options to only the tunnel interface. In my case this was tun0. Then also use ipleaks ``torrent address detection`` to ensure you are maintaining privacy. Also consider enabling qBittorrents anonymous mode.
5
+
6
+
## Usage
7
+
8
+
### Example Values
9
+
10
+
To create a qbittorrent client with your VPN you can use the following values as a rough guide. You will need to change the storage, and the host to match your own needs. You will also need to bring your own secret. In the following configuration I use the ``gluetun`` secret. This will be mounted with every key as environment variables to configure your gluetun setup. See https://github.com/qdm12/gluetun-wiki/tree/main/setup/providers for environment variables you will need to add to this secret.
0 commit comments