diff --git a/bitnami/valkey/CHANGELOG.md b/bitnami/valkey/CHANGELOG.md index a62ea00543..fc5071a07f 100644 --- a/bitnami/valkey/CHANGELOG.md +++ b/bitnami/valkey/CHANGELOG.md @@ -1,8 +1,12 @@ # Changelog -## 3.0.31 (2025-08-23) +## 4.0.1 (2025-09-03) -* [bitnami/valkey] :zap: :arrow_up: Update dependency references ([#36174](https://github.com/bitnami/charts/pull/36174)) +* [bitnami/valkey] doc: fix default value in README ([#35741](https://github.com/bitnami/charts/pull/35741)) + +## 3.0.31 (2025-08-23) + +* [bitnami/valkey] :zap: :arrow_up: Update dependency references (#36174) ([bfa74fb](https://github.com/bitnami/charts/commit/bfa74fb5cb43be45e0238a6fc4db88ae4dad4f78)), closes [#36174](https://github.com/bitnami/charts/issues/36174) ## 3.0.30 (2025-08-14) diff --git a/bitnami/valkey/Chart.yaml b/bitnami/valkey/Chart.yaml index 2e102622b1..97d51df9c5 100644 --- a/bitnami/valkey/Chart.yaml +++ b/bitnami/valkey/Chart.yaml @@ -38,4 +38,4 @@ maintainers: name: valkey sources: - https://github.com/bitnami/charts/tree/main/bitnami/valkey -version: 4.0.0 +version: 4.0.1 diff --git a/bitnami/valkey/README.md b/bitnami/valkey/README.md index 862d0906f7..6e4d5235f5 100644 --- a/bitnami/valkey/README.md +++ b/bitnami/valkey/README.md @@ -2,7 +2,7 @@ # Bitnami package for Valkey -Valkey is an open source (BSD) high-performance key/value datastore that supports a variety workloads such as caching, message queues, and can act as a primary database. +Valkey is an open source (BSD) high-performance key/value datastore that supports a variety of workloads such as caching, message queues, and can act as a primary database. [Overview of Valkey](https://valkey.io/) @@ -55,7 +55,7 @@ The command deploys Valkey on the Kubernetes cluster in the default configuratio ### Resource requests and limits -Bitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case. +Bitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads, and these should be adapted to your specific use case. To make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/). @@ -160,7 +160,7 @@ When installing the chart with `architecture=standalone`, it will deploy a stand When installing the chart with `architecture=replication` and `sentinel.enabled=true`, it will deploy a single Valkey StatefulSet. In this case, the pods will contain an extra container with Valkey Sentinel. This container will form a cluster of Valkey Sentinel nodes, which will promote a new primary in case the actual one fails. -On graceful termination of the Valkey primary pod, a failover of the primary is initiated to promote a new primary. The Valkey Sentinel container in this pod will wait for the failover to occur before terminating. If `sentinel.valkeyShutdownWaitFailover=true` is set (the default), the Valkey container will wait for the failover as well before terminating. This increases availability for reads during failover, but may cause stale reads until all clients have switched to the new primary. +On graceful termination of the Valkey primary pod, failover of the primary is initiated to promote a new primary. The Valkey Sentinel container in this pod will wait for the failover to occur before terminating. If `sentinel.valkeyShutdownWaitFailover=true` is set (the default), the Valkey container will wait for the failover as well before terminating. This increases availability for reads during failover, but may cause stale reads until all clients have switched to the new primary. In addition to this, only one service is exposed: @@ -169,7 +169,7 @@ In addition to this, only one service is exposed: For read-only operations, access the service using port 6379. For write operations, it's necessary to access the Valkey Sentinel cluster and query the current primary using the command below (using valkey-cli or similar): ```console -SENTINEL get-primary-addr-by-name +SENTINEL get-primary-addr-by-name ``` This command will return the address of the current primary, which can be accessed from inside the cluster. @@ -194,7 +194,7 @@ It's recommended to only change `primary.replicaCount` if you know what you are ### Using a password file -To use a password file for Valkey you need to create a secret containing the password and then deploy the chart using that secret. Follow these instructions: +To use a password file for Valkey, you need to create a secret containing the password and then deploy the chart using that secret. Follow these instructions: - Create the secret with the password. It is important that the file with the password must be called `valkey-password`. @@ -224,7 +224,7 @@ TLS support can be enabled in the chart by specifying the `tls.` parameters whil For example: -First, create the secret with the certificates files: +First, create the secret with the certificate files: ```console kubectl create secret generic certificates-tls-secret --from-file=./cert.pem --from-file=./cert.key --from-file=./ca.pem @@ -242,7 +242,7 @@ tls.certCAFilename="ca.pem" ### Metrics -The chart optionally can start a metrics exporter for [prometheus](https://prometheus.io). The metrics endpoint (port 9121) is exposed in the service. Metrics can be scraped from within the cluster using something similar as the described in the [example Prometheus scrape configuration](https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml). If metrics are to be scraped from outside the cluster, the Kubernetes API proxy can be utilized to access the endpoint. +The chart optionally can start a metrics exporter for [prometheus](https://prometheus.io). The metrics endpoint (port 9121) is exposed in the service. Metrics can be scraped from within the cluster using something similar as the described in the [example Prometheus scrape configuration](https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml). If metrics are to be scraped from outside the cluster, the Kubernetes API proxy can be used to access the endpoint. If you have enabled TLS by specifying `tls.enabled=true` you also need to specify TLS option to the metrics exporter. You can do that via `metrics.extraArgs`. You can find the metrics exporter CLI flags for TLS [here](https://github.com/oliver006/valkey_exporter#command-line-flags). For example: @@ -301,9 +301,9 @@ Note that this will not disable transparent huge tables. ### Backup and restore -To backup and restore Valkey deployments on Kubernetes, you will need to create a snapshot of the data in the source cluster, and later restore it in a new cluster with the new parameters. Follow the instructions below: +To back up and restore Valkey deployments on Kubernetes, you will need to create a snapshot of the data in the source cluster, and later restore it in a new cluster with the new parameters. Follow the instructions below: -#### Step 1: Backup the deployment +#### Step 1: Back up the deployment - Connect to one of the nodes and start the Valkey CLI tool. Then, run the commands below: @@ -338,15 +338,15 @@ Follow the following steps: save "" ``` - > *Note that the `Enable AOF` comment belongs to the original config file and what you're actually doing is disabling it. This change will only be neccessary for the temporal cluster you're creating to upload the dump.* + > *Note that the `Enable AOF` comment belongs to the original config file and what you're actually doing is disabling it. This change will only be necessary for the temporal cluster you're creating to upload the dump.* - Start the new cluster to create the PVCs. Use the command below as an example: ```console - helm install new-valkey -f values.yaml . --set cluster.enabled=true --set cluster.replicaCount=3 + helm install new-valkey -f values.yaml . --set cluster.enabled=true --set cluster.replicaCount=3 ``` -- Now that the PVC were created, stop it and copy the *dump.rdp* file on the persisted data by using a helping pod. +- Now that the PVC is created, stop it and copy the *dump.rdp* file on the persisted data by using a helping pod. ```text $ helm delete new-valkey @@ -470,14 +470,14 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R ### Valkey Image parameters -| Name | Description | Value | -| ------------------- | ------------------------------------------------------------------------------------------------------ | ------------------------ | -| `image.registry` | Valkey image registry | `REGISTRY_NAME` | -| `image.repository` | Valkey image repository | `REPOSITORY_NAME/valkey` | -| `image.digest` | Valkey image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | -| `image.pullPolicy` | Valkey image pull policy | `IfNotPresent` | -| `image.pullSecrets` | Valkey image pull secrets | `[]` | -| `image.debug` | Enable image debug mode | `false` | +| Name | Description | Value | +| ------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------ | +| `image.registry` | Valkey image registry | `REGISTRY_NAME` | +| `image.repository` | Valkey image repository | `REPOSITORY_NAME/valkey` | +| `image.digest` | Valkey image digest in the way sha256:aa... Please note this parameter, if set, will override the tag | `""` | +| `image.pullPolicy` | Valkey image pull policy | `IfNotPresent` | +| `image.pullSecrets` | Valkey image pull secrets | `[]` | +| `image.debug` | Enable image debug mode | `false` | ### Valkey common configuration parameters @@ -533,12 +533,12 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `primary.customReadinessProbe` | Custom readinessProbe that overrides the default one | `{}` | | `primary.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if primary.resources is set (primary.resources is recommended for production). | `nano` | | `primary.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | -| `primary.podSecurityContext.enabled` | Enabled Valkey primary pods' Security Context | `true` | +| `primary.podSecurityContext.enabled` | Enable Valkey primary pods' Security Context | `true` | | `primary.podSecurityContext.fsGroupChangePolicy` | Set filesystem group change policy | `Always` | | `primary.podSecurityContext.sysctls` | Set kernel settings using the sysctl interface | `[]` | | `primary.podSecurityContext.supplementalGroups` | Set filesystem extra groups | `[]` | | `primary.podSecurityContext.fsGroup` | Set Valkey primary pod's Security Context fsGroup | `1001` | -| `primary.containerSecurityContext.enabled` | Enabled Valkey primary containers' Security Context | `true` | +| `primary.containerSecurityContext.enabled` | Enable Valkey primary containers' Security Context | `true` | | `primary.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | | `primary.containerSecurityContext.runAsUser` | Set Valkey primary containers' Security Context runAsUser | `1001` | | `primary.containerSecurityContext.runAsGroup` | Set Valkey primary containers' Security Context runAsGroup | `1001` | @@ -569,8 +569,8 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `primary.dnsPolicy` | DNS Policy for Valkey primary pod | `""` | | `primary.dnsConfig` | DNS Configuration for Valkey primary pod | `{}` | | `primary.lifecycleHooks` | for the Valkey primary container(s) to automate configuration before or after startup | `{}` | -| `primary.extraVolumes` | Optionally specify extra list of additional volumes for the Valkey primary pod(s) | `[]` | -| `primary.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Valkey primary container(s) | `[]` | +| `primary.extraVolumes` | Optionally, specify extra list of additional volumes for the Valkey primary pod(s) | `[]` | +| `primary.extraVolumeMounts` | Optionally, specify extra list of additional volumeMounts for the Valkey primary container(s) | `[]` | | `primary.sidecars` | Add additional sidecar containers to the Valkey primary pod(s) | `[]` | | `primary.initContainers` | Add additional init containers to the Valkey primary pod(s) | `[]` | | `primary.persistence.enabled` | Enable persistence on Valkey primary nodes using Persistent Volume Claims | `true` | @@ -586,7 +586,7 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `primary.persistence.labels` | Additional custom labels for the PVC | `{}` | | `primary.persistence.selector` | Additional labels to match for the PVC | `{}` | | `primary.persistence.dataSource` | Custom PVC data source | `{}` | -| `primary.persistence.existingClaim` | Use a existing PVC which must be created manually before bound | `""` | +| `primary.persistence.existingClaim` | Use an existing PVC which must be created manually before bound | `""` | | `primary.persistentVolumeClaimRetentionPolicy.enabled` | Controls if and how PVCs are deleted during the lifecycle of a StatefulSet | `false` | | `primary.persistentVolumeClaimRetentionPolicy.whenScaled` | Volume retention behavior when the replica count of the StatefulSet is reduced | `Retain` | | `primary.persistentVolumeClaimRetentionPolicy.whenDeleted` | Volume retention behavior that applies when the StatefulSet is deleted | `Retain` | @@ -656,12 +656,12 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `replica.customReadinessProbe` | Custom readinessProbe that overrides the default one | `{}` | | `replica.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if replica.resources is set (replica.resources is recommended for production). | `nano` | | `replica.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | -| `replica.podSecurityContext.enabled` | Enabled Valkey replicas pods' Security Context | `true` | +| `replica.podSecurityContext.enabled` | Enable Valkey replicas pods' Security Context | `true` | | `replica.podSecurityContext.fsGroupChangePolicy` | Set filesystem group change policy | `Always` | | `replica.podSecurityContext.sysctls` | Set kernel settings using the sysctl interface | `[]` | | `replica.podSecurityContext.supplementalGroups` | Set filesystem extra groups | `[]` | | `replica.podSecurityContext.fsGroup` | Set Valkey replicas pod's Security Context fsGroup | `1001` | -| `replica.containerSecurityContext.enabled` | Enabled Valkey replicas containers' Security Context | `true` | +| `replica.containerSecurityContext.enabled` | Enable Valkey replicas containers' Security Context | `true` | | `replica.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | | `replica.containerSecurityContext.runAsUser` | Set Valkey replicas containers' Security Context runAsUser | `1001` | | `replica.containerSecurityContext.runAsGroup` | Set Valkey replicas containers' Security Context runAsGroup | `1001` | @@ -692,8 +692,8 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `replica.dnsPolicy` | DNS Policy for Valkey replica pods | `""` | | `replica.dnsConfig` | DNS Configuration for Valkey replica pods | `{}` | | `replica.lifecycleHooks` | for the Valkey replica container(s) to automate configuration before or after startup | `{}` | -| `replica.extraVolumes` | Optionally specify extra list of additional volumes for the Valkey replicas pod(s) | `[]` | -| `replica.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Valkey replicas container(s) | `[]` | +| `replica.extraVolumes` | Optionally, specify an extra list of additional volumes for the Valkey replicas pod(s) | `[]` | +| `replica.extraVolumeMounts` | Optionally, specify extra list of additional volumeMounts for the Valkey replicas container(s) | `[]` | | `replica.sidecars` | Add additional sidecar containers to the Valkey replicas pod(s) | `[]` | | `replica.initContainers` | Add additional init containers to the Valkey replicas pod(s) | `[]` | | `replica.persistence.enabled` | Enable persistence on Valkey replicas nodes using Persistent Volume Claims | `true` | @@ -709,7 +709,7 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `replica.persistence.labels` | Additional custom labels for the PVC | `{}` | | `replica.persistence.selector` | Additional labels to match for the PVC | `{}` | | `replica.persistence.dataSource` | Custom PVC data source | `{}` | -| `replica.persistence.existingClaim` | Use a existing PVC which must be created manually before bound | `""` | +| `replica.persistence.existingClaim` | Use an existing PVC which must be created manually before bound | `""` | | `replica.persistentVolumeClaimRetentionPolicy.enabled` | Controls if and how PVCs are deleted during the lifecycle of a StatefulSet | `false` | | `replica.persistentVolumeClaimRetentionPolicy.whenScaled` | Volume retention behavior when the replica count of the StatefulSet is reduced | `Retain` | | `replica.persistentVolumeClaimRetentionPolicy.whenDeleted` | Volume retention behavior that applies when the StatefulSet is deleted | `Retain` | @@ -771,11 +771,11 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `sentinel.primarySet` | Primary set name | `myprimary` | | `sentinel.quorum` | Sentinel Quorum | `2` | | `sentinel.getPrimaryTimeout` | Amount of time to allow before get_sentinel_primary_info() times out. | `90` | -| `sentinel.automateClusterRecovery` | Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it. | `false` | +| `sentinel.automateClusterRecovery` | Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically fail over to it. | `false` | | `sentinel.valkeyShutdownWaitFailover` | Whether the Valkey primary container waits for the failover at shutdown (in addition to the Valkey Sentinel container). | `true` | | `sentinel.downAfterMilliseconds` | Timeout for detecting a Valkey node is down | `60000` | -| `sentinel.failoverTimeout` | Timeout for performing a election failover | `180000` | -| `sentinel.parallelSyncs` | Number of replicas that can be reconfigured in parallel to use the new primary after a failover | `1` | +| `sentinel.failoverTimeout` | Timeout for performing the election failover | `180000` | +| `sentinel.parallelSyncs` | Number of replicas that can be reconfigured in parallel to use the new primary after the failover | `1` | | `sentinel.configuration` | Configuration for Valkey Sentinel nodes | `""` | | `sentinel.command` | Override default container command (useful when using custom images) | `[]` | | `sentinel.args` | Override default container args (useful when using custom images) | `[]` | @@ -824,7 +824,7 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `sentinel.persistentVolumeClaimRetentionPolicy.whenDeleted` | Volume retention behavior that applies when the StatefulSet is deleted | `Retain` | | `sentinel.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if sentinel.resources is set (sentinel.resources is recommended for production). | `nano` | | `sentinel.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | -| `sentinel.containerSecurityContext.enabled` | Enabled Valkey Sentinel containers' Security Context | `true` | +| `sentinel.containerSecurityContext.enabled` | Enable Valkey Sentinel containers' Security Context | `true` | | `sentinel.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | | `sentinel.containerSecurityContext.runAsUser` | Set Valkey Sentinel containers' Security Context runAsUser | `1001` | | `sentinel.containerSecurityContext.runAsGroup` | Set Valkey Sentinel containers' Security Context runAsGroup | `1001` | @@ -834,8 +834,8 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `sentinel.containerSecurityContext.seccompProfile.type` | Set Valkey Sentinel containers' Security Context seccompProfile | `RuntimeDefault` | | `sentinel.containerSecurityContext.capabilities.drop` | Set Valkey Sentinel containers' Security Context capabilities to drop | `["ALL"]` | | `sentinel.lifecycleHooks` | for the Valkey sentinel container(s) to automate configuration before or after startup | `{}` | -| `sentinel.extraVolumes` | Optionally specify extra list of additional volumes for the Valkey Sentinel | `[]` | -| `sentinel.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Valkey Sentinel container(s) | `[]` | +| `sentinel.extraVolumes` | Optionally, specify extra list of additional volumes for the Valkey Sentinel | `[]` | +| `sentinel.extraVolumeMounts` | Optionally, specify extra list of additional volumeMounts for the Valkey Sentinel container(s) | `[]` | | `sentinel.service.type` | Valkey Sentinel service type | `ClusterIP` | | `sentinel.service.ports.valkey` | Valkey service port for Valkey | `6379` | | `sentinel.service.ports.sentinel` | Valkey service port for Valkey Sentinel | `26379` | @@ -885,99 +885,99 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `tls.certFilename` | Certificate filename | `""` | | `tls.certKeyFilename` | Certificate Key filename | `""` | | `tls.certCAFilename` | CA Certificate filename | `""` | -| `tls.dhParamsFilename` | File containing DH params (in order to support DH based ciphers) | `""` | +| `tls.dhParamsFilename` | File containing DH params (to support DH-based ciphers) | `""` | ### Metrics Parameters -| Name | Description | Value | -| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | -| `metrics.enabled` | Start a sidecar prometheus exporter to expose Valkey metrics | `false` | -| `metrics.image.registry` | Valkey Exporter image registry | `REGISTRY_NAME` | -| `metrics.image.repository` | Valkey Exporter image repository | `REPOSITORY_NAME/valkey-exporter` | -| `metrics.image.digest` | Valkey Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | -| `metrics.image.pullPolicy` | Valkey Exporter image pull policy | `IfNotPresent` | -| `metrics.image.pullSecrets` | Valkey Exporter image pull secrets | `[]` | -| `metrics.containerPorts.http` | Metrics HTTP container port | `9121` | -| `metrics.startupProbe.enabled` | Enable startupProbe on Valkey replicas nodes | `false` | -| `metrics.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `10` | -| `metrics.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` | -| `metrics.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `5` | -| `metrics.startupProbe.failureThreshold` | Failure threshold for startupProbe | `5` | -| `metrics.startupProbe.successThreshold` | Success threshold for startupProbe | `1` | -| `metrics.livenessProbe.enabled` | Enable livenessProbe on Valkey replicas nodes | `true` | -| `metrics.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `10` | -| `metrics.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` | -| `metrics.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` | -| `metrics.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` | -| `metrics.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` | -| `metrics.readinessProbe.enabled` | Enable readinessProbe on Valkey replicas nodes | `true` | -| `metrics.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` | -| `metrics.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `10` | -| `metrics.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` | -| `metrics.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `3` | -| `metrics.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` | -| `metrics.customStartupProbe` | Custom startupProbe that overrides the default one | `{}` | -| `metrics.customLivenessProbe` | Custom livenessProbe that overrides the default one | `{}` | -| `metrics.customReadinessProbe` | Custom readinessProbe that overrides the default one | `{}` | -| `metrics.command` | Override default metrics container init command (useful when using custom images) | `[]` | -| `metrics.valkeyTargetHost` | A way to specify an alternative Valkey hostname | `localhost` | -| `metrics.extraArgs` | Extra arguments for Valkey exporter, for example: | `{}` | -| `metrics.extraEnvVars` | Array with extra environment variables to add to Valkey exporter | `[]` | -| `metrics.containerSecurityContext.enabled` | Enabled Valkey exporter containers' Security Context | `true` | -| `metrics.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | -| `metrics.containerSecurityContext.runAsUser` | Set Valkey exporter containers' Security Context runAsUser | `1001` | -| `metrics.containerSecurityContext.runAsGroup` | Set Valkey exporter containers' Security Context runAsGroup | `1001` | -| `metrics.containerSecurityContext.runAsNonRoot` | Set Valkey exporter containers' Security Context runAsNonRoot | `true` | -| `metrics.containerSecurityContext.allowPrivilegeEscalation` | Set Valkey exporter containers' Security Context allowPrivilegeEscalation | `false` | -| `metrics.containerSecurityContext.readOnlyRootFilesystem` | Set container's Security Context read-only root filesystem | `true` | -| `metrics.containerSecurityContext.seccompProfile.type` | Set Valkey exporter containers' Security Context seccompProfile | `RuntimeDefault` | -| `metrics.containerSecurityContext.capabilities.drop` | Set Valkey exporter containers' Security Context capabilities to drop | `["ALL"]` | -| `metrics.extraVolumes` | Optionally specify extra list of additional volumes for the Valkey metrics sidecar | `[]` | -| `metrics.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Valkey metrics sidecar | `[]` | -| `metrics.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if metrics.resources is set (metrics.resources is recommended for production). | `nano` | -| `metrics.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | -| `metrics.podLabels` | Extra labels for Valkey exporter pods | `{}` | -| `metrics.podAnnotations` | Annotations for Valkey exporter pods | `{}` | -| `metrics.service.enabled` | Create Service resource(s) for scraping metrics using PrometheusOperator ServiceMonitor, can be disabled when using a PodMonitor | `true` | -| `metrics.service.type` | Valkey exporter service type | `ClusterIP` | -| `metrics.service.ports.http` | Valkey exporter service port | `9121` | -| `metrics.service.externalTrafficPolicy` | Valkey exporter service external traffic policy | `Cluster` | -| `metrics.service.extraPorts` | Extra ports to expose (normally used with the `sidecar` value) | `[]` | -| `metrics.service.loadBalancerIP` | Valkey exporter service Load Balancer IP | `""` | -| `metrics.service.loadBalancerClass` | exporter service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific) | `""` | -| `metrics.service.loadBalancerSourceRanges` | Valkey exporter service Load Balancer sources | `[]` | -| `metrics.service.annotations` | Additional custom annotations for Valkey exporter service | `{}` | -| `metrics.service.clusterIP` | Valkey exporter service Cluster IP | `""` | -| `metrics.serviceMonitor.port` | the service port to scrape metrics from | `http-metrics` | -| `metrics.serviceMonitor.enabled` | Create ServiceMonitor resource(s) for scraping metrics using PrometheusOperator | `false` | -| `metrics.serviceMonitor.namespace` | The namespace in which the ServiceMonitor will be created | `""` | -| `metrics.serviceMonitor.interval` | The interval at which metrics should be scraped | `30s` | -| `metrics.serviceMonitor.scrapeTimeout` | The timeout after which the scrape is ended | `""` | -| `metrics.serviceMonitor.relabelings` | Metrics RelabelConfigs to apply to samples before scraping. | `[]` | -| `metrics.serviceMonitor.metricRelabelings` | Metrics RelabelConfigs to apply to samples before ingestion. | `[]` | -| `metrics.serviceMonitor.honorLabels` | Specify honorLabels parameter to add the scrape endpoint | `false` | -| `metrics.serviceMonitor.additionalLabels` | Additional labels that can be used so ServiceMonitor resource(s) can be discovered by Prometheus | `{}` | -| `metrics.serviceMonitor.podTargetLabels` | Labels from the Kubernetes pod to be transferred to the created metrics | `[]` | -| `metrics.serviceMonitor.sampleLimit` | Limit of how many samples should be scraped from every Pod | `false` | -| `metrics.serviceMonitor.targetLimit` | Limit of how many targets should be scraped | `false` | -| `metrics.serviceMonitor.additionalEndpoints` | Additional endpoints to scrape (e.g sentinel) | `[]` | -| `metrics.podMonitor.port` | the pod port to scrape metrics from | `metrics` | -| `metrics.podMonitor.enabled` | Create PodMonitor resource(s) for scraping metrics using PrometheusOperator | `false` | -| `metrics.podMonitor.namespace` | The namespace in which the PodMonitor will be created | `""` | -| `metrics.podMonitor.interval` | The interval at which metrics should be scraped | `30s` | -| `metrics.podMonitor.scrapeTimeout` | The timeout after which the scrape is ended | `""` | -| `metrics.podMonitor.relabelings` | Metrics RelabelConfigs to apply to samples before scraping. | `[]` | -| `metrics.podMonitor.metricRelabelings` | Metrics RelabelConfigs to apply to samples before ingestion. | `[]` | -| `metrics.podMonitor.honorLabels` | Specify honorLabels parameter to add the scrape endpoint | `false` | -| `metrics.podMonitor.additionalLabels` | Additional labels that can be used so PodMonitor resource(s) can be discovered by Prometheus | `{}` | -| `metrics.podMonitor.podTargetLabels` | Labels from the Kubernetes pod to be transferred to the created metrics | `[]` | -| `metrics.podMonitor.sampleLimit` | Limit of how many samples should be scraped from every Pod | `false` | -| `metrics.podMonitor.targetLimit` | Limit of how many targets should be scraped | `false` | -| `metrics.podMonitor.additionalEndpoints` | Additional endpoints to scrape (e.g sentinel) | `[]` | -| `metrics.prometheusRule.enabled` | Create a custom prometheusRule Resource for scraping metrics using PrometheusOperator | `false` | -| `metrics.prometheusRule.namespace` | The namespace in which the prometheusRule will be created | `""` | -| `metrics.prometheusRule.additionalLabels` | Additional labels for the prometheusRule | `{}` | -| `metrics.prometheusRule.rules` | Custom Prometheus rules | `[]` | +| Name | Description | Value | +| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- | +| `metrics.enabled` | Start a sidecar Prometheus Exporter to expose Valkey metrics | `false` | +| `metrics.image.registry` | Redis(R) Exporter image registry | `REGISTRY_NAME` | +| `metrics.image.repository` | Redis(R) Exporter image repository | `REPOSITORY_NAME/redis-exporter` | +| `metrics.image.digest` | Redis(R) Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | +| `metrics.image.pullPolicy` | Redis(R) Exporter image pull policy | `IfNotPresent` | +| `metrics.image.pullSecrets` | Redis(R) Exporter image pull secrets | `[]` | +| `metrics.containerPorts.http` | Metrics HTTP container port | `9121` | +| `metrics.startupProbe.enabled` | Enable startupProbe on Valkey replicas nodes | `false` | +| `metrics.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `10` | +| `metrics.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` | +| `metrics.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `5` | +| `metrics.startupProbe.failureThreshold` | Failure threshold for startupProbe | `5` | +| `metrics.startupProbe.successThreshold` | Success threshold for startupProbe | `1` | +| `metrics.livenessProbe.enabled` | Enable livenessProbe on Valkey replicas nodes | `true` | +| `metrics.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `10` | +| `metrics.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` | +| `metrics.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` | +| `metrics.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` | +| `metrics.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` | +| `metrics.readinessProbe.enabled` | Enable readinessProbe on Valkey replicas nodes | `true` | +| `metrics.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` | +| `metrics.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `10` | +| `metrics.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` | +| `metrics.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `3` | +| `metrics.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` | +| `metrics.customStartupProbe` | Custom startupProbe that overrides the default one | `{}` | +| `metrics.customLivenessProbe` | Custom livenessProbe that overrides the default one | `{}` | +| `metrics.customReadinessProbe` | Custom readinessProbe that overrides the default one | `{}` | +| `metrics.command` | Override default metrics container init command (useful when using custom images) | `[]` | +| `metrics.valkeyTargetHost` | A way to specify an alternative Valkey hostname | `localhost` | +| `metrics.extraArgs` | Extra arguments for Redis(R) Exporter | `{}` | +| `metrics.extraEnvVars` | Array with extra environment variables to add to Redis(R) Exporter | `[]` | +| `metrics.containerSecurityContext.enabled` | Enable Redis(R) Exporter containers' Security Context | `true` | +| `metrics.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | +| `metrics.containerSecurityContext.runAsUser` | Set Redis(R) Exporter containers' Security Context runAsUser | `1001` | +| `metrics.containerSecurityContext.runAsGroup` | Set Redis(R) Exporter containers' Security Context runAsGroup | `1001` | +| `metrics.containerSecurityContext.runAsNonRoot` | Set Redis(R) Exporter containers' Security Context runAsNonRoot | `true` | +| `metrics.containerSecurityContext.allowPrivilegeEscalation` | Set Redis(R) Exporter containers' Security Context allowPrivilegeEscalation | `false` | +| `metrics.containerSecurityContext.readOnlyRootFilesystem` | Set container's Security Context read-only root filesystem | `true` | +| `metrics.containerSecurityContext.seccompProfile.type` | Set Redis(R) Exporter containers' Security Context seccompProfile | `RuntimeDefault` | +| `metrics.containerSecurityContext.capabilities.drop` | Set Redis(R) Exporter containers' Security Context capabilities to drop | `["ALL"]` | +| `metrics.extraVolumes` | Optionally, specify extra list of additional volumes for the Valkey metrics sidecar | `[]` | +| `metrics.extraVolumeMounts` | Optionally, specify extra list of additional volumeMounts for the Valkey metrics sidecar | `[]` | +| `metrics.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if metrics.resources is set (metrics.resources is recommended for production). | `nano` | +| `metrics.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | +| `metrics.podLabels` | Extra labels for Redis(R) Exporter pods | `{}` | +| `metrics.podAnnotations` | Annotations for Redis(R) Exporter pods | `{}` | +| `metrics.service.enabled` | Create Service resource(s) for scraping metrics using PrometheusOperator ServiceMonitor, can be disabled when using a PodMonitor | `true` | +| `metrics.service.type` | Redis(R) Exporter service type | `ClusterIP` | +| `metrics.service.ports.http` | Redis(R) Exporter service port | `9121` | +| `metrics.service.externalTrafficPolicy` | Redis(R) Exporter service external traffic policy | `Cluster` | +| `metrics.service.extraPorts` | Extra ports to expose (normally used with the `sidecar` value) | `[]` | +| `metrics.service.loadBalancerIP` | Redis(R) Exporter service Load Balancer IP | `""` | +| `metrics.service.loadBalancerClass` | Exporter service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific) | `""` | +| `metrics.service.loadBalancerSourceRanges` | Redis(R) Exporter service Load Balancer sources | `[]` | +| `metrics.service.annotations` | Additional custom annotations for Redis(R) Exporter service | `{}` | +| `metrics.service.clusterIP` | Redis(R) Exporter service Cluster IP | `""` | +| `metrics.serviceMonitor.port` | the service port to scrape metrics from | `http-metrics` | +| `metrics.serviceMonitor.enabled` | Create ServiceMonitor resource(s) for scraping metrics using PrometheusOperator | `false` | +| `metrics.serviceMonitor.namespace` | The namespace in which the ServiceMonitor will be created | `""` | +| `metrics.serviceMonitor.interval` | The interval at which metrics should be scraped | `30s` | +| `metrics.serviceMonitor.scrapeTimeout` | The timeout after which the scrape is ended | `""` | +| `metrics.serviceMonitor.relabelings` | Metrics RelabelConfigs to apply to samples before scraping. | `[]` | +| `metrics.serviceMonitor.metricRelabelings` | Metrics RelabelConfigs to apply to samples before ingestion. | `[]` | +| `metrics.serviceMonitor.honorLabels` | Specify honorLabels parameter to add the scrape endpoint | `false` | +| `metrics.serviceMonitor.additionalLabels` | Additional labels that can be used so ServiceMonitor resource(s) can be discovered by Prometheus | `{}` | +| `metrics.serviceMonitor.podTargetLabels` | Labels from the Kubernetes pod to be transferred to the created metrics | `[]` | +| `metrics.serviceMonitor.sampleLimit` | Limit of how many samples should be scraped from every Pod | `false` | +| `metrics.serviceMonitor.targetLimit` | Limit of how many targets should be scraped | `false` | +| `metrics.serviceMonitor.additionalEndpoints` | Additional endpoints to scrape (e.g., sentinel) | `[]` | +| `metrics.podMonitor.port` | the pod port to scrape metrics from | `metrics` | +| `metrics.podMonitor.enabled` | Create PodMonitor resource(s) for scraping metrics using PrometheusOperator | `false` | +| `metrics.podMonitor.namespace` | The namespace in which the PodMonitor will be created | `""` | +| `metrics.podMonitor.interval` | The interval at which metrics should be scraped | `30s` | +| `metrics.podMonitor.scrapeTimeout` | The timeout after which the scrape is ended | `""` | +| `metrics.podMonitor.relabelings` | Metrics RelabelConfigs to apply to samples before scraping. | `[]` | +| `metrics.podMonitor.metricRelabelings` | Metrics RelabelConfigs to apply to samples before ingestion. | `[]` | +| `metrics.podMonitor.honorLabels` | Specify honorLabels parameter to add the scrape endpoint | `false` | +| `metrics.podMonitor.additionalLabels` | Additional labels that can be used so PodMonitor resource(s) can be discovered by Prometheus | `{}` | +| `metrics.podMonitor.podTargetLabels` | Labels from the Kubernetes pod to be transferred to the created metrics | `[]` | +| `metrics.podMonitor.sampleLimit` | Limit of how many samples should be scraped from every Pod | `false` | +| `metrics.podMonitor.targetLimit` | Limit of how many targets should be scraped | `false` | +| `metrics.podMonitor.additionalEndpoints` | Additional endpoints to scrape (e.g., sentinel) | `[]` | +| `metrics.prometheusRule.enabled` | Create a custom prometheusRule Resource for scraping metrics using PrometheusOperator | `false` | +| `metrics.prometheusRule.namespace` | The namespace in which the prometheusRule will be created | `""` | +| `metrics.prometheusRule.additionalLabels` | Additional labels for the prometheusRule | `{}` | +| `metrics.prometheusRule.rules` | Custom Prometheus rules | `[]` | ### Init Container Parameters @@ -999,7 +999,7 @@ helm install my-release --set primary.persistence.existingClaim=PVC_NAME oci://R | `kubectl.image.pullPolicy` | Kubectl image pull policy | `IfNotPresent` | | `kubectl.image.pullSecrets` | Kubectl pull secrets | `[]` | | `kubectl.command` | kubectl command to execute | `["/opt/bitnami/scripts/kubectl-scripts/update-primary-label.sh"]` | -| `kubectl.containerSecurityContext.enabled` | Enabled kubectl containers' Security Context | `true` | +| `kubectl.containerSecurityContext.enabled` | Enable kubectl containers' Security Context | `true` | | `kubectl.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | | `kubectl.containerSecurityContext.runAsUser` | Set kubectl containers' Security Context runAsUser | `1001` | | `kubectl.containerSecurityContext.runAsGroup` | Set kubectl containers' Security Context runAsGroup | `1001` | diff --git a/bitnami/valkey/values.yaml b/bitnami/valkey/values.yaml index 6e637be6a1..3b82ede63c 100644 --- a/bitnami/valkey/values.yaml +++ b/bitnami/valkey/values.yaml @@ -15,7 +15,7 @@ ## global: imageRegistry: "" - ## E.g. + ## Example: ## imagePullSecrets: ## - myRegistryKeySecretName ## @@ -102,7 +102,7 @@ diagnosticMode: ## @param image.registry [default: REGISTRY_NAME] Valkey image registry ## @param image.repository [default: REPOSITORY_NAME/valkey] Valkey image repository ## @skip image.tag Valkey image tag (immutable tags are recommended) -## @param image.digest Valkey image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag +## @param image.digest Valkey image digest in the way sha256:aa... Please note this parameter, if set, will override the tag ## @param image.pullPolicy Valkey image pull policy ## @param image.pullSecrets Valkey image pull secrets ## @param image.debug Enable image debug mode @@ -116,10 +116,10 @@ image: ## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images ## pullPolicy: IfNotPresent - ## Optionally specify an array of imagePullSecrets. + ## Optionally, specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ - ## e.g: + ## Example: ## pullSecrets: ## - myRegistryKeySecretName ## @@ -203,14 +203,14 @@ primary: ## preExecCmds: [] ## @param primary.extraFlags Array with additional command line flags for Valkey primary - ## e.g: + ## Example: ## extraFlags: ## - "--maxmemory-policy volatile-ttl" ## - "--repl-backlog-size 1024mb" ## extraFlags: [] ## @param primary.extraEnvVars Array with extra environment variables to add to Valkey primary nodes - ## e.g: + ## Example: ## extraEnvVars: ## - name: FOO ## value: "bar" @@ -298,7 +298,7 @@ primary: resources: {} ## Configure Pods Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param primary.podSecurityContext.enabled Enabled Valkey primary pods' Security Context + ## @param primary.podSecurityContext.enabled Enable Valkey primary pods' Security Context ## @param primary.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy ## @param primary.podSecurityContext.sysctls Set kernel settings using the sysctl interface ## @param primary.podSecurityContext.supplementalGroups Set filesystem extra groups @@ -312,7 +312,7 @@ primary: fsGroup: 1001 ## Configure Container Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param primary.containerSecurityContext.enabled Enabled Valkey primary containers' Security Context + ## @param primary.containerSecurityContext.enabled Enable Valkey primary containers' Security Context ## @param primary.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container ## @param primary.containerSecurityContext.runAsUser Set Valkey primary containers' Security Context runAsUser ## @param primary.containerSecurityContext.runAsGroup Set Valkey primary containers' Security Context runAsGroup @@ -395,7 +395,7 @@ primary: ## key: "" ## @param primary.nodeAffinityPreset.values Node label values to match. Ignored if `primary.affinity` is set - ## E.g. + ## Example: ## values: ## - e2e-az1 ## - e2e-az2 @@ -416,7 +416,7 @@ primary: tolerations: [] ## @param primary.topologySpreadConstraints Spread Constraints for Valkey primary pod assignment ## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/ - ## E.g. + ## Example: ## topologySpreadConstraints: ## - maxSkew: 1 ## topologyKey: node @@ -425,13 +425,13 @@ primary: topologySpreadConstraints: [] ## @param primary.dnsPolicy DNS Policy for Valkey primary pod ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ - ## E.g. + ## Example: ## dnsPolicy: ClusterFirst ## dnsPolicy: "" ## @param primary.dnsConfig DNS Configuration for Valkey primary pod ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ - ## E.g. + ## Example: ## dnsConfig: ## options: ## - name: ndots @@ -442,14 +442,14 @@ primary: ## @param primary.lifecycleHooks for the Valkey primary container(s) to automate configuration before or after startup ## lifecycleHooks: {} - ## @param primary.extraVolumes Optionally specify extra list of additional volumes for the Valkey primary pod(s) + ## @param primary.extraVolumes Optionally, specify extra list of additional volumes for the Valkey primary pod(s) ## extraVolumes: [] - ## @param primary.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Valkey primary container(s) + ## @param primary.extraVolumeMounts Optionally, specify extra list of additional volumeMounts for the Valkey primary container(s) ## extraVolumeMounts: [] ## @param primary.sidecars Add additional sidecar containers to the Valkey primary pod(s) - ## e.g: + ## Example: ## sidecars: ## - name: your-image-name ## image: your-image @@ -461,7 +461,7 @@ primary: sidecars: [] ## @param primary.initContainers Add additional init containers to the Valkey primary pod(s) ## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ - ## e.g: + ## Example: ## initContainers: ## - name: your-image-name ## image: your-image @@ -513,7 +513,7 @@ primary: ## labels: {} ## @param primary.persistence.selector Additional labels to match for the PVC - ## e.g: + ## Example: ## selector: ## matchLabels: ## app: my-app @@ -522,7 +522,7 @@ primary: ## @param primary.persistence.dataSource Custom PVC data source ## dataSource: {} - ## @param primary.persistence.existingClaim Use a existing PVC which must be created manually before bound + ## @param primary.persistence.existingClaim Use an existing PVC which must be created manually before bound ## NOTE: requires primary.persistence.enabled: true ## existingClaim: "" @@ -576,14 +576,14 @@ primary: loadBalancerClass: "" ## @param primary.service.loadBalancerSourceRanges Valkey primary service Load Balancer sources ## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service - ## e.g. + ## Example: ## loadBalancerSourceRanges: ## - 10.10.10.0/24 ## loadBalancerSourceRanges: [] ## @param primary.service.externalIPs Valkey primary service External IPs ## https://kubernetes.io/docs/concepts/services-networking/service/#external-ips - ## e.g. + ## Example: ## externalIPs: ## - 10.10.10.1 ## - 201.22.30.1 @@ -668,14 +668,14 @@ replica: ## preExecCmds: [] ## @param replica.extraFlags Array with additional command line flags for Valkey replicas - ## e.g: + ## Example: ## extraFlags: ## - "--maxmemory-policy volatile-ttl" ## - "--repl-backlog-size 1024mb" ## extraFlags: [] ## @param replica.extraEnvVars Array with extra environment variables to add to Valkey replicas nodes - ## e.g: + ## Example: ## extraEnvVars: ## - name: FOO ## value: "bar" @@ -771,7 +771,7 @@ replica: resources: {} ## Configure Pods Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param replica.podSecurityContext.enabled Enabled Valkey replicas pods' Security Context + ## @param replica.podSecurityContext.enabled Enable Valkey replicas pods' Security Context ## @param replica.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy ## @param replica.podSecurityContext.sysctls Set kernel settings using the sysctl interface ## @param replica.podSecurityContext.supplementalGroups Set filesystem extra groups @@ -785,7 +785,7 @@ replica: fsGroup: 1001 ## Configure Container Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param replica.containerSecurityContext.enabled Enabled Valkey replicas containers' Security Context + ## @param replica.containerSecurityContext.enabled Enable Valkey replicas containers' Security Context ## @param replica.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container ## @param replica.containerSecurityContext.runAsUser Set Valkey replicas containers' Security Context runAsUser ## @param replica.containerSecurityContext.runAsGroup Set Valkey replicas containers' Security Context runAsGroup @@ -868,7 +868,7 @@ replica: ## key: "" ## @param replica.nodeAffinityPreset.values Node label values to match. Ignored if `replica.affinity` is set - ## E.g. + ## Example: ## values: ## - e2e-az1 ## - e2e-az2 @@ -889,7 +889,7 @@ replica: tolerations: [] ## @param replica.topologySpreadConstraints Spread Constraints for Valkey replicas pod assignment ## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/ - ## E.g. + ## Example: ## topologySpreadConstraints: ## - maxSkew: 1 ## topologyKey: node @@ -898,13 +898,13 @@ replica: topologySpreadConstraints: [] ## @param replica.dnsPolicy DNS Policy for Valkey replica pods ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ - ## E.g. + ## Example: ## dnsPolicy: ClusterFirst ## dnsPolicy: "" ## @param replica.dnsConfig DNS Configuration for Valkey replica pods ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ - ## E.g. + ## Example: ## dnsConfig: ## options: ## - name: ndots @@ -915,14 +915,14 @@ replica: ## @param replica.lifecycleHooks for the Valkey replica container(s) to automate configuration before or after startup ## lifecycleHooks: {} - ## @param replica.extraVolumes Optionally specify extra list of additional volumes for the Valkey replicas pod(s) + ## @param replica.extraVolumes Optionally, specify an extra list of additional volumes for the Valkey replicas pod(s) ## extraVolumes: [] - ## @param replica.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Valkey replicas container(s) + ## @param replica.extraVolumeMounts Optionally, specify extra list of additional volumeMounts for the Valkey replicas container(s) ## extraVolumeMounts: [] ## @param replica.sidecars Add additional sidecar containers to the Valkey replicas pod(s) - ## e.g: + ## Example: ## sidecars: ## - name: your-image-name ## image: your-image @@ -934,7 +934,7 @@ replica: sidecars: [] ## @param replica.initContainers Add additional init containers to the Valkey replicas pod(s) ## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ - ## e.g: + ## Example: ## initContainers: ## - name: your-image-name ## image: your-image @@ -986,7 +986,7 @@ replica: ## labels: {} ## @param replica.persistence.selector Additional labels to match for the PVC - ## e.g: + ## Example: ## selector: ## matchLabels: ## app: my-app @@ -995,7 +995,7 @@ replica: ## @param replica.persistence.dataSource Custom PVC data source ## dataSource: {} - ## @param replica.persistence.existingClaim Use a existing PVC which must be created manually before bound + ## @param replica.persistence.existingClaim Use an existing PVC which must be created manually before bound ## NOTE: requires replica.persistence.enabled: true ## existingClaim: "" @@ -1049,7 +1049,7 @@ replica: loadBalancerClass: "" ## @param replica.service.loadBalancerSourceRanges Valkey replicas service Load Balancer sources ## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service - ## e.g. + ## Example: ## loadBalancerSourceRanges: ## - 10.10.10.0/24 ## @@ -1063,6 +1063,7 @@ replica: ## sessionAffinity: None ## @param replica.service.sessionAffinityConfig Additional settings for the sessionAffinity + ## Example: ## sessionAffinityConfig: ## clientIP: ## timeoutSeconds: 300 @@ -1086,12 +1087,18 @@ replica: ## controlledResources: [] ## @param replica.autoscaling.vpa.maxAllowed VPA Max allowed resources for the pod - ## cpu: 200m - ## memory: 100Mi + ## Example: + ## maxAllowed: + ## cpu: 200m + ## memory: 100Mi + ## maxAllowed: {} ## @param replica.autoscaling.vpa.minAllowed VPA Min allowed resources for the pod - ## cpu: 200m - ## memory: 100Mi + ## Example: + ## maxAllowed: + ## cpu: 200m + ## memory: 100Mi + ## minAllowed: {} ## @section VPA update policy ## @@ -1172,10 +1179,10 @@ sentinel: ## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images ## pullPolicy: IfNotPresent - ## Optionally specify an array of imagePullSecrets. + ## Optionally, specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ - ## e.g: + ## Example: ## pullSecrets: ## - myRegistryKeySecretName ## @@ -1195,7 +1202,7 @@ sentinel: ## @param sentinel.getPrimaryTimeout Amount of time to allow before get_sentinel_primary_info() times out. ## getPrimaryTimeout: 90 - ## @param sentinel.automateClusterRecovery Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it. + ## @param sentinel.automateClusterRecovery Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically fail over to it. ## This also prevents any new replica from starting until the last remaining replica is elected as primary to guarantee that it is the one to be elected by Sentinel, and not a newly started replica with no data. ## NOTE: This feature requires a "downAfterMilliseconds" value less or equal to 2000. ## @@ -1205,11 +1212,11 @@ sentinel: valkeyShutdownWaitFailover: true ## Sentinel timing restrictions ## @param sentinel.downAfterMilliseconds Timeout for detecting a Valkey node is down - ## @param sentinel.failoverTimeout Timeout for performing a election failover + ## @param sentinel.failoverTimeout Timeout for performing the election failover ## downAfterMilliseconds: 60000 failoverTimeout: 180000 - ## @param sentinel.parallelSyncs Number of replicas that can be reconfigured in parallel to use the new primary after a failover + ## @param sentinel.parallelSyncs Number of replicas that can be reconfigured in parallel to use the new primary after the failover ## parallelSyncs: 1 ## @param sentinel.configuration Configuration for Valkey Sentinel nodes @@ -1229,7 +1236,7 @@ sentinel: ## preExecCmds: [] ## @param sentinel.extraEnvVars Array with extra environment variables to add to Valkey Sentinel nodes - ## e.g: + ## Example: ## extraEnvVars: ## - name: FOO ## value: "bar" @@ -1333,7 +1340,7 @@ sentinel: ## labels: {} ## @param sentinel.persistence.selector Additional labels to match for the PVC - ## e.g: + ## Example: ## selector: ## matchLabels: ## app: my-app @@ -1377,7 +1384,7 @@ sentinel: resources: {} ## Configure Container Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param sentinel.containerSecurityContext.enabled Enabled Valkey Sentinel containers' Security Context + ## @param sentinel.containerSecurityContext.enabled Enable Valkey Sentinel containers' Security Context ## @param sentinel.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container ## @param sentinel.containerSecurityContext.runAsUser Set Valkey Sentinel containers' Security Context runAsUser ## @param sentinel.containerSecurityContext.runAsGroup Set Valkey Sentinel containers' Security Context runAsGroup @@ -1402,10 +1409,10 @@ sentinel: ## @param sentinel.lifecycleHooks for the Valkey sentinel container(s) to automate configuration before or after startup ## lifecycleHooks: {} - ## @param sentinel.extraVolumes Optionally specify extra list of additional volumes for the Valkey Sentinel + ## @param sentinel.extraVolumes Optionally, specify extra list of additional volumes for the Valkey Sentinel ## extraVolumes: [] - ## @param sentinel.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Valkey Sentinel container(s) + ## @param sentinel.extraVolumeMounts Optionally, specify extra list of additional volumeMounts for the Valkey Sentinel container(s) ## extraVolumeMounts: [] ## Valkey Sentinel service parameters @@ -1456,7 +1463,7 @@ sentinel: loadBalancerClass: "" ## @param sentinel.service.loadBalancerSourceRanges Valkey Sentinel service Load Balancer sources ## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service - ## e.g. + ## Example: ## loadBalancerSourceRanges: ## - 10.10.10.0/24 ## @@ -1470,6 +1477,7 @@ sentinel: ## sessionAffinity: None ## @param sentinel.service.sessionAffinityConfig Additional settings for the sessionAffinity + ## Example: ## sessionAffinityConfig: ## clientIP: ## timeoutSeconds: 300 @@ -1509,7 +1517,7 @@ networkPolicy: ## allowExternalEgress: true ## @param networkPolicy.extraIngress Add extra ingress rules to the NetworkPolicy - ## e.g: + ## Example: ## extraIngress: ## - ports: ## - port: 1234 @@ -1526,7 +1534,7 @@ networkPolicy: ## extraIngress: [] ## @param networkPolicy.extraEgress Add extra egress rules to the NetworkPolicy - ## e.g: + ## Example: ## extraEgress: ## - ports: ## - port: 1234 @@ -1574,7 +1582,7 @@ rbac: ## create: false ## @param rbac.rules Custom RBAC rules to set - ## e.g: + ## Example: ## rules: ## - apiGroups: ## - "" @@ -1631,23 +1639,23 @@ tls: ## @param tls.certCAFilename CA Certificate filename ## certCAFilename: "" - ## @param tls.dhParamsFilename File containing DH params (in order to support DH based ciphers) + ## @param tls.dhParamsFilename File containing DH params (to support DH-based ciphers) ## dhParamsFilename: "" ## @section Metrics Parameters ## metrics: - ## @param metrics.enabled Start a sidecar prometheus exporter to expose Valkey metrics + ## @param metrics.enabled Start a sidecar Prometheus Exporter to expose Valkey metrics ## enabled: false - ## Bitnami Valkey Exporter image - ## ref: https://hub.docker.com/r/bitnami/valkey-exporter/tags/ - ## @param metrics.image.registry [default: REGISTRY_NAME] Valkey Exporter image registry - ## @param metrics.image.repository [default: REPOSITORY_NAME/valkey-exporter] Valkey Exporter image repository - ## @skip metrics.image.tag Valkey Exporter image tag (immutable tags are recommended) - ## @param metrics.image.digest Valkey Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag - ## @param metrics.image.pullPolicy Valkey Exporter image pull policy - ## @param metrics.image.pullSecrets Valkey Exporter image pull secrets + ## Bitnami Redis(R) Exporter image + ## ref: https://hub.docker.com/r/bitnami/redis-exporter/tags/ + ## @param metrics.image.registry [default: REGISTRY_NAME] Redis(R) Exporter image registry + ## @param metrics.image.repository [default: REPOSITORY_NAME/redis-exporter] Redis(R) Exporter image repository + ## @skip metrics.image.tag Redis(R) Exporter image tag (immutable tags are recommended) + ## @param metrics.image.digest Redis(R) Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag + ## @param metrics.image.pullPolicy Redis(R) Exporter image pull policy + ## @param metrics.image.pullSecrets Redis(R) Exporter image pull secrets ## image: registry: docker.io @@ -1655,10 +1663,10 @@ metrics: tag: 1.76.0-debian-12-r0 digest: "" pullPolicy: IfNotPresent - ## Optionally specify an array of imagePullSecrets. + ## Optionally, specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ - ## e.g: + ## Example: ## pullSecrets: ## - myRegistryKeySecretName ## @@ -1727,14 +1735,14 @@ metrics: ## Useful for certificate CN/SAN matching ## valkeyTargetHost: "localhost" - ## @param metrics.extraArgs Extra arguments for Valkey exporter, for example: - ## e.g.: + ## @param metrics.extraArgs Extra arguments for Redis(R) Exporter + ## Example: ## extraArgs: ## check-keys: myKey,myOtherKey ## extraArgs: {} - ## @param metrics.extraEnvVars Array with extra environment variables to add to Valkey exporter - ## e.g: + ## @param metrics.extraEnvVars Array with extra environment variables to add to Redis(R) Exporter + ## Example: ## extraEnvVars: ## - name: FOO ## value: "bar" @@ -1742,15 +1750,15 @@ metrics: extraEnvVars: [] ## Configure Container Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param metrics.containerSecurityContext.enabled Enabled Valkey exporter containers' Security Context + ## @param metrics.containerSecurityContext.enabled Enable Redis(R) Exporter containers' Security Context ## @param metrics.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container - ## @param metrics.containerSecurityContext.runAsUser Set Valkey exporter containers' Security Context runAsUser - ## @param metrics.containerSecurityContext.runAsGroup Set Valkey exporter containers' Security Context runAsGroup - ## @param metrics.containerSecurityContext.runAsNonRoot Set Valkey exporter containers' Security Context runAsNonRoot - ## @param metrics.containerSecurityContext.allowPrivilegeEscalation Set Valkey exporter containers' Security Context allowPrivilegeEscalation + ## @param metrics.containerSecurityContext.runAsUser Set Redis(R) Exporter containers' Security Context runAsUser + ## @param metrics.containerSecurityContext.runAsGroup Set Redis(R) Exporter containers' Security Context runAsGroup + ## @param metrics.containerSecurityContext.runAsNonRoot Set Redis(R) Exporter containers' Security Context runAsNonRoot + ## @param metrics.containerSecurityContext.allowPrivilegeEscalation Set Redis(R) Exporter containers' Security Context allowPrivilegeEscalation ## @param metrics.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem - ## @param metrics.containerSecurityContext.seccompProfile.type Set Valkey exporter containers' Security Context seccompProfile - ## @param metrics.containerSecurityContext.capabilities.drop Set Valkey exporter containers' Security Context capabilities to drop + ## @param metrics.containerSecurityContext.seccompProfile.type Set Redis(R) Exporter containers' Security Context seccompProfile + ## @param metrics.containerSecurityContext.capabilities.drop Set Redis(R) Exporter containers' Security Context capabilities to drop ## containerSecurityContext: enabled: true @@ -1764,13 +1772,13 @@ metrics: type: RuntimeDefault capabilities: drop: ["ALL"] - ## @param metrics.extraVolumes Optionally specify extra list of additional volumes for the Valkey metrics sidecar + ## @param metrics.extraVolumes Optionally, specify extra list of additional volumes for the Valkey metrics sidecar ## extraVolumes: [] - ## @param metrics.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Valkey metrics sidecar + ## @param metrics.extraVolumeMounts Optionally, specify extra list of additional volumeMounts for the Valkey metrics sidecar ## extraVolumeMounts: [] - ## Valkey exporter resource requests and limits + ## Redis(R) Exporter resource requests and limits ## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/ ## @param metrics.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if metrics.resources is set (metrics.resources is recommended for production). ## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15 @@ -1787,55 +1795,55 @@ metrics: ## memory: 1024Mi ## resources: {} - ## @param metrics.podLabels Extra labels for Valkey exporter pods + ## @param metrics.podLabels Extra labels for Redis(R) Exporter pods ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ ## podLabels: {} - ## @param metrics.podAnnotations [object] Annotations for Valkey exporter pods + ## @param metrics.podAnnotations [object] Annotations for Redis(R) Exporter pods ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/ ## podAnnotations: prometheus.io/scrape: "true" prometheus.io/port: "9121" - ## Valkey exporter service parameters + ## Redis(R) Exporter service parameters ## service: ## @param metrics.service.enabled Create Service resource(s) for scraping metrics using PrometheusOperator ServiceMonitor, can be disabled when using a PodMonitor ## enabled: true - ## @param metrics.service.type Valkey exporter service type + ## @param metrics.service.type Redis(R) Exporter service type ## type: ClusterIP - ## @param metrics.service.ports.http Valkey exporter service port + ## @param metrics.service.ports.http Redis(R) Exporter service port ## ports: http: 9121 - ## @param metrics.service.externalTrafficPolicy Valkey exporter service external traffic policy + ## @param metrics.service.externalTrafficPolicy Redis(R) Exporter service external traffic policy ## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip ## externalTrafficPolicy: Cluster ## @param metrics.service.extraPorts Extra ports to expose (normally used with the `sidecar` value) ## extraPorts: [] - ## @param metrics.service.loadBalancerIP Valkey exporter service Load Balancer IP + ## @param metrics.service.loadBalancerIP Redis(R) Exporter service Load Balancer IP ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer ## loadBalancerIP: "" - ## @param metrics.service.loadBalancerClass exporter service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific) + ## @param metrics.service.loadBalancerClass Exporter service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific) ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer ## loadBalancerClass: "" - ## @param metrics.service.loadBalancerSourceRanges Valkey exporter service Load Balancer sources + ## @param metrics.service.loadBalancerSourceRanges Redis(R) Exporter service Load Balancer sources ## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service - ## e.g. + ## Example: ## loadBalancerSourceRanges: ## - 10.10.10.0/24 ## loadBalancerSourceRanges: [] - ## @param metrics.service.annotations Additional custom annotations for Valkey exporter service + ## @param metrics.service.annotations Additional custom annotations for Redis(R) Exporter service ## annotations: {} - ## @param metrics.service.clusterIP Valkey exporter service Cluster IP + ## @param metrics.service.clusterIP Redis(R) Exporter service Cluster IP ## clusterIP: "" ## Prometheus Service Monitor @@ -1879,19 +1887,20 @@ metrics: ## @param metrics.serviceMonitor.targetLimit Limit of how many targets should be scraped ## targetLimit: false - ## @param metrics.serviceMonitor.additionalEndpoints Additional endpoints to scrape (e.g sentinel) + ## @param metrics.serviceMonitor.additionalEndpoints Additional endpoints to scrape (e.g., sentinel) + ## Example to scrape sentinel metrics, also to in order distinguish between Sentinel and Valkey container metrics + ## add metricRelabelings with label like app=valkey to main valkey pod-monitor port: + ## additionalEndpoints: + ## - interval: "30s" + ## path: "/scrape" + ## port: "metrics" + ## params: + ## target: ["localhost:26379"] + ## metricRelabelings: + ## - targetLabel: "app" + ## replacement: "sentinel" ## additionalEndpoints: [] - # uncomment in order to scrape sentinel metrics, also to in order distinguish between Sentinel and Valkey container metrics - # add metricRelabelings with label like app=valkey to main valkey pod-monitor port - # - interval: "30s" - # path: "/scrape" - # port: "metrics" - # params: - # target: ["localhost:26379"] - # metricRelabelings: - # - targetLabel: "app" - # replacement: "sentinel" ## Prometheus Pod Monitor ## ref: https://github.com/coreos/prometheus-operator ## https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#podmonitor @@ -1916,10 +1925,12 @@ metrics: ## relabelings: [] ## @param metrics.podMonitor.metricRelabelings Metrics RelabelConfigs to apply to samples before ingestion. + ## Example: + ## metricRelabelings: + ## - targetLabel: "app" + ## replacement: "valkey" ## metricRelabelings: [] - # - targetLabel: "app" - # replacement: "valkey" ## @param metrics.podMonitor.honorLabels Specify honorLabels parameter to add the scrape endpoint ## honorLabels: false @@ -1935,17 +1946,19 @@ metrics: ## @param metrics.podMonitor.targetLimit Limit of how many targets should be scraped ## targetLimit: false - ## @param metrics.podMonitor.additionalEndpoints Additional endpoints to scrape (e.g sentinel) + ## @param metrics.podMonitor.additionalEndpoints Additional endpoints to scrape (e.g., sentinel) + ## Example: + ## additionalEndpoints: + ## - interval: "30s" + ## path: "/scrape" + ## port: "metrics" + ## params: + ## target: ["localhost:26379"] + ## metricRelabelings: + ## - targetLabel: "app" + ## replacement: "sentinel" ## additionalEndpoints: [] - # - interval: "30s" - # path: "/scrape" - # port: "metrics" - # params: - # target: ["localhost:26379"] - # metricRelabelings: - # - targetLabel: "app" - # replacement: "sentinel" ## Custom PrometheusRule to be defined ## ref: https://github.com/coreos/prometheus-operator#customresourcedefinitions ## @@ -1960,7 +1973,7 @@ metrics: ## additionalLabels: {} ## @param metrics.prometheusRule.rules Custom Prometheus rules - ## e.g: + ## Example: ## rules: ## - alert: ValkeyDown ## expr: valkey_up{service="{{ template "common.names.fullname" . }}-metrics"} == 0 @@ -2021,10 +2034,10 @@ volumePermissions: tag: 12-debian-12-r51 digest: "" pullPolicy: IfNotPresent - ## Optionally specify an array of imagePullSecrets. + ## Optionally, specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ - ## e.g: + ## Example: ## pullSecrets: ## - myRegistryKeySecretName ## @@ -2046,7 +2059,7 @@ volumePermissions: ## memory: 1024Mi ## resources: {} - ## Init container Container Security Context + ## Init container Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container ## @param volumePermissions.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container ## @param volumePermissions.containerSecurityContext.runAsUser Set init container's Security Context runAsUser @@ -2080,10 +2093,10 @@ kubectl: ## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images ## pullPolicy: IfNotPresent - ## Optionally specify an array of imagePullSecrets. + ## Optionally, specify an array of imagePullSecrets. ## Secrets must be manually created in the namespace. ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ - ## e.g: + ## Example: ## pullSecrets: ## - myRegistryKeySecretName ## @@ -2093,7 +2106,7 @@ kubectl: command: ["/opt/bitnami/scripts/kubectl-scripts/update-primary-label.sh"] ## Configure Container Security Context ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod - ## @param kubectl.containerSecurityContext.enabled Enabled kubectl containers' Security Context + ## @param kubectl.containerSecurityContext.enabled Enable kubectl containers' Security Context ## @param kubectl.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container ## @param kubectl.containerSecurityContext.runAsUser Set kubectl containers' Security Context runAsUser ## @param kubectl.containerSecurityContext.runAsGroup Set kubectl containers' Security Context runAsGroup