mirror of
https://github.com/k8s-at-home/charts.git
synced 2025-01-24 07:59:02 +00:00
document breaking change (#202)
This commit is contained in:
parent
590dbb9135
commit
9848d64e43
@ -2,7 +2,7 @@ apiVersion: v1
|
|||||||
appVersion: "v0.6"
|
appVersion: "v0.6"
|
||||||
description: DNS proxy as ad-blocker for local network
|
description: DNS proxy as ad-blocker for local network
|
||||||
name: blocky
|
name: blocky
|
||||||
version: 2.3.0
|
version: 3.0.0
|
||||||
keywords:
|
keywords:
|
||||||
- blocky
|
- blocky
|
||||||
- dbs
|
- dbs
|
||||||
|
@ -46,3 +46,29 @@ Alternatively, a YAML file that specifies the values for the above parameters ca
|
|||||||
```console
|
```console
|
||||||
helm install --name blocky -f values.yaml billimek/blocky
|
helm install --name blocky -f values.yaml billimek/blocky
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Upgrading an existing Release to a new major version
|
||||||
|
|
||||||
|
A major chart version change (like 2.2.2 -> 3.0.0) indicates that there is an
|
||||||
|
incompatible breaking change needing manual actions.
|
||||||
|
|
||||||
|
### Upgrading from 2.x.x to 3.x.x
|
||||||
|
|
||||||
|
Due to the renaming of the service port, an upgrade-in-place will not work. The following are possible approaches to solve this:
|
||||||
|
|
||||||
|
#### Helm force upgrade
|
||||||
|
|
||||||
|
```sh
|
||||||
|
helm upgrade --force
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Delete the existing `blocky` service prior to upgrading
|
||||||
|
|
||||||
|
```sh
|
||||||
|
kubectl delete svc/blocky
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Remove the existing blocky chart first
|
||||||
|
|
||||||
|
This is the 'easiest' approach, but will incur downtime which can be problematic if you rely on blocky for DNS
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user