volker.raschek/reposilite-charts
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(README): adapt stakaters reloader example

Browse Source
This commit is contained in:
Markus Pesch
2025-11-30 10:46:28 +01:00
parent c066cbfca7
commit 96e604f79e
1 changed files with 8 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@@ -97,24 +97,19 @@ helm install --version "${CHART_VERSION}" reposilite volker.raschek/reposilite \
#### TLS certificate rotation #### TLS certificate rotation
If Reposilite uses TLS certificates that are mounted as a secret in the container file system like the example If Reposilite uses TLS certificates that are mounted as a secret in the container file system like the example
[above](#tls-encryption), Reposlite will not automatically apply them when the TLS certificates are rotated. Such a [above](#tls-encryption), Reposilite will not automatically apply them when the TLS certificates are rotated. Such a
rotation can be for example triggered, when the [cert-manager](https://cert-manager.io/) issues new TLS certificates rotation can be for example triggered, when the [cert-manager](https://cert-manager.io/) issues new TLS certificates
before expiring. before expiring.
Until Reposilite does not support rotating TLS certificate a workaround can be applied. For example stakater's Until Reposilite does not support rotating TLS certificate a workaround can be applied. For example stakater's
[reloader](https://github.com/stakater/Reloader) controller can be used to trigger a rolling update. The following [reloader](https://github.com/stakater/Reloader) controller can be used to trigger a rolling update. The following
annotation must be added to instruct the reloader controller to trigger a rolling update, when the mounted configMaps annotation must be added to instruct the reloader controller to trigger a rolling update, when the mounted secret has
and secrets have been changed. been changed.
```yaml > [!IMPORTANT]
deployment: > The Helm chart already adds annotations to trigger a rolling release. Helm describes this approach under
annotations: > [Automatically Roll Deployments](https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments).
reloader.stakater.com/auto: "true" > For this reason, **only external** configMaps or secrets need to be monitored by reloader.
```
Instead of triggering a rolling update for configMap and secret resources, this action can also be defined for
individual items. For example, when the secret named `reposilite-tls` is mounted and the reloader controller should only
listen for changes of this secret:
```yaml ```yaml
deployment: deployment:
@@ -132,8 +127,8 @@ stakater's reloader.
```diff ```diff
deployment: deployment:
annotations: annotations:
reloader.stakater.com/auto: "true"
+ reloader.stakater.com/rollout-strategy: "restart" + reloader.stakater.com/rollout-strategy: "restart"
secret.reloader.stakater.com/reload: "reposilite-tls"
``` ```
#### Network policies #### Network policies