|
@@ -183,13 +183,14 @@ If managing TLS secrets outside of Helm, it is possible to create a TLS secret (
|
|
|
|
|
|
### Global parameters
|
|
|
|
|
|
-| Name | Description | Value |
|
|
|
-| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ |
|
|
|
-| `global.imageRegistry` | Global Docker image registry | `""` |
|
|
|
-| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |
|
|
|
-| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `""` |
|
|
|
-| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `""` |
|
|
|
-| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |
|
|
|
+| Name | Description | Value |
|
|
|
+| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
|
|
|
+| `global.imageRegistry` | Global Docker image registry | `""` |
|
|
|
+| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |
|
|
|
+| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `""` |
|
|
|
+| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `""` |
|
|
|
+| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |
|
|
|
+| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |
|
|
|
|
|
|
### Common parameters
|
|
|
|
|
@@ -532,6 +533,10 @@ Find more information about how to deal with common errors related to Bitnami's
|
|
|
|
|
|
## Upgrading
|
|
|
|
|
|
+### To 2.3.0
|
|
|
+
|
|
|
+This version introduces image verification for security purposes. To disable it, set `global.security.allowInsecureImages` to `true`. More details at [GitHub issue](https://github.com/bitnami/charts/issues/30850).
|
|
|
+
|
|
|
### To 2.0.0
|
|
|
|
|
|
This major bump changes the following security defaults:
|