[bitnami/kiam] Detect non-standard images (#30900)

* [bitnami/kiam] Detect non-standard images

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

* Update CHANGELOG.md

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

* Update NOTES.txt

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

---------

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Carlos Rodríguez Hernández
2024-12-10 19:15:49 +01:00
committed by GitHub
co-authored by Bitnami Containers
parent 3764aee648
commit 802c8ceb74
6 changed files with 31 additions and 14 deletions
+8 -2
View File
@@ -1,8 +1,14 @@
# Changelog
## 2.2.18 (2024-12-04)
## 2.3.0 (2024-12-10)
* [bitnami/kiam] Release 2.2.18 ([#30762](https://github.com/bitnami/charts/pull/30762))
* [bitnami/kiam] Detect non-standard images ([#30900](https://github.com/bitnami/charts/pull/30900))
## <small>2.2.18 (2024-12-04)</small>
* [bitnami/*] docs: :memo: Add "Backup & Restore" section (#30711) ([35ab536](https://github.com/bitnami/charts/commit/35ab5363741e7548f4076f04da6e62d10153c60c)), closes [#30711](https://github.com/bitnami/charts/issues/30711)
* [bitnami/*] docs: :memo: Add "Prometheus metrics" (batch 3) (#30666) ([82fc7e2](https://github.com/bitnami/charts/commit/82fc7e2fc12e2648ed22069942203c02bf5d4cc6)), closes [#30666](https://github.com/bitnami/charts/issues/30666)
* [bitnami/kiam] Release 2.2.18 (#30762) ([654bb09](https://github.com/bitnami/charts/commit/654bb09d1137cb21c52f275da787fecb9a5e818f)), closes [#30762](https://github.com/bitnami/charts/issues/30762)
## <small>2.2.17 (2024-11-07)</small>
+3 -3
View File
@@ -1,6 +1,6 @@
dependencies:
- name: common
repository: oci://registry-1.docker.io/bitnamicharts
version: 2.27.2
digest: sha256:6fd86cc5a4b5094abca1f23c8ec064e75e51eceaded94a5e20977274b2abb576
generated: "2024-12-04T01:57:39.712793992Z"
version: 2.28.0
digest: sha256:5b30f0fa07bb89b01c55fd6258c8ce22a611b13623d4ad83e8fdd1d4490adc74
generated: "2024-12-10T17:07:40.078844+01:00"
+1 -1
View File
@@ -28,4 +28,4 @@ maintainers:
name: kiam
sources:
- https://github.com/bitnami/charts/tree/main/bitnami/kiam
version: 2.2.18
version: 2.3.0
+12 -7
View File
@@ -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:
+1
View File
@@ -135,3 +135,4 @@ In order to associate your pods with AWS IAM roles, follow the steps below:
{{- include "kiam.validateValues" . }}
{{- include "common.warnings.resources" (dict "sections" (list "agent" "server") "context" $) }}
{{- include "common.warnings.modifiedImages" (dict "images" (list .Values.image) "context" $) }}
{{- include "common.errors.insecureImages" (dict "images" (list .Values.image) "context" $) }}
+5
View File
@@ -20,6 +20,11 @@ global:
imagePullSecrets: []
defaultStorageClass: ""
storageClass: ""
## Security parameters
##
security:
## @param global.security.allowInsecureImages Allows skipping image verification
allowInsecureImages: false
## Compatibility adaptations for Kubernetes platforms
##
compatibility: