mirror of
https://github.com/bitnami/charts.git
synced 2026-03-11 07:17:45 +08:00
[bitnami/kube-prometheus] Added missing upgradePath documentation (#6633)
* added objectstorageConfig to the sidecar container * Bumped version and added documentation of the added values. * Fixed indentation of environment variables * Rename ConfigMap to Secret and added to production-values * Fixed missing space * Added more security to kube-prometheus * More security * Added support for containerSecurityContext on prometheus-operator CRDs. * Added ability to configure readinessProbes ans livenessProbes * Added proper liveness and readiness probes * Added documentation for the values.yaml * Changed documentation to reference podSecurityContext * More documentation * Bump major version * Fixed wrong value reference * Added documentation for thanos liveness readinessProbe * Use the http port instead of web * Fixed liveness and readinessProbe * Fixed ambigious liveness and readiness probes to be explicit when chaining. * Make rootFilesystem unsecure again. (This is only needed for bitnamis current internal testing * Added documentation for the Upgrade path to 6.0.0
This commit is contained in:
@@ -580,6 +580,33 @@ Find more information about how to deal with common errors related to Bitnami’
|
||||
```bash
|
||||
$ helm upgrade my-release bitnami/kube-prometheus
|
||||
```
|
||||
### To 6.0.0
|
||||
|
||||
This major update changes the `securityContext` interface in the `values.yaml` file.
|
||||
|
||||
Please note if you have changes in the `securityContext` fields those need to be migrated to `podSecurityContext`.
|
||||
|
||||
```diff
|
||||
# ...
|
||||
- securityContext:
|
||||
+ podSecurityContext:
|
||||
# ...
|
||||
```
|
||||
|
||||
Other than that a new `securityContext` interface for containers got introduced `containerSecurityContext`. It's default is enabled so if you do not need it you need to opt out of it.
|
||||
|
||||
If you use [Strategic Merge Patch](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/strategic-merge-patch.md) for any of the
|
||||
`Alertmanager` or `Prometheus` kinds you need to actively disable all of those things below. For the resource you want to use Strategic Merge Patch for.
|
||||
|
||||
```yaml
|
||||
<resource>:
|
||||
containerSecurityContext:
|
||||
enabled: false
|
||||
livenessProbe:
|
||||
enabled: false
|
||||
readinessProbe:
|
||||
enabled: false
|
||||
```
|
||||
|
||||
### To 5.0.0
|
||||
|
||||
|
||||
Reference in New Issue
Block a user