dentaku/woodpecker-helm3
1
0
Fork 0
Code Pull requests Releases Activity

Recommend removing tiller when upgrading [#8]

Browse source
This commit is contained in:
Erin Call 2019-12-23 09:57:05 -08:00
parent 3d1c849e75
commit 59a591eda5
No known key found for this signature in database
GPG key ID: 4071FF6C15B8DAD1
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -58,7 +58,11 @@ steps:
The setting names for drone-helm3 are backwards-compatible with those for drone-helm, so the only mandatory step is to update the `image` clause so that drone uses the new plugin. The setting names for drone-helm3 are backwards-compatible with those for drone-helm, so the only mandatory step is to update the `image` clause so that drone uses the new plugin.
There are several settings that no longer have any effect: There are some recommended changes, though:
* If your `service_account` is currently `tiller`, change it to a service account with more restricted permissions.
* If possible, remove the tiller account entirely, since its superuser status presents a security risk.
* Remove outdated settings that have no effect in drone-helm3:
* `purge` -- this is the default behavior in Helm 3 * `purge` -- this is the default behavior in Helm 3
* `recreate_pods` * `recreate_pods`
@ -67,5 +71,3 @@ There are several settings that no longer have any effect:
* `canary_image` * `canary_image`
* `client_only` * `client_only`
* `stable_repo_url` * `stable_repo_url`
If your `.drone.yml` contains those settings, we recommend removing them.