Skip to content

Commit

Permalink
Merge pull request #454 from percona/K8SPSMDB-1224-psmdb-1190
Browse files Browse the repository at this point in the history
K8SPSMDB-1124 - Update PSMDB charts for 1.19.0 release
  • Loading branch information
jvpasinatto authored Jan 21, 2025
2 parents e038d85 + 7806135 commit 147d57a
Show file tree
Hide file tree
Showing 8 changed files with 110 additions and 25 deletions.
8 changes: 4 additions & 4 deletions charts/psmdb-db/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
apiVersion: v2
appVersion: "1.18.0"
appVersion: "1.19.0"
description: A Helm chart for installing Percona Server MongoDB Cluster Databases using the PSMDB Operator.
name: psmdb-db
home: https://www.percona.com/doc/kubernetes-operator-for-psmongodb/index.html
version: 1.18.0
version: 1.19.0
maintainers:
- name: tplavcic
email: [email protected]
- name: nmarukovich
email: [email protected]
- name: jvpasinatto
email: [email protected]
16 changes: 11 additions & 5 deletions charts/psmdb-db/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,14 +23,14 @@ To install the chart with the `psmdb` release name using a dedicated namespace (

```sh
helm repo add percona https://percona.github.io/percona-helm-charts/
helm install my-db percona/psmdb-db --version 1.18.0 --namespace my-namespace
helm install my-db percona/psmdb-db --version 1.19.0 --namespace my-namespace
```

The chart can be customized using the following configurable parameters:

| Parameter | Description | Default |
| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
| `crVersion` | CR Cluster Manifest version | `1.18.0` |
| `crVersion` | CR Cluster Manifest version | `1.19.0` |
| `pause` | Stop PSMDB Database safely | `false` |
| `unmanaged` | Start cluster and don't manage it (cross cluster replication) | `false` |
| `enableVolumeExpansion` | Allows to resize `PersistentVolumeClaim`s by changing `.volumeSpec.persistentVolumeClaim.resources` field | `false` |
Expand All @@ -55,7 +55,7 @@ The chart can be customized using the following configurable parameters:
| `finalizers:percona.com/delete-psmdb-pods-in-order` | Set this if you want to delete PSMDB pods in order (primary last) | `[]` |
| `finalizers:percona.com/delete-pitr-chunks` | Set this if you want to delete all pitr chunks on cluster deletion | `[]` |
| `image.repository` | PSMDB Container image repository | `percona/percona-server-mongodb` |
| `image.tag` | PSMDB Container image tag | `7.0.14-8-multi` |
| `image.tag` | PSMDB Container image tag | `8.0.4-1-multi` |
| `imagePullPolicy` | The policy used to update images | `Always` |
| `imagePullSecrets` | PSMDB Container pull secret | `[]` |
| `initImage.repository` | Repository for custom init image | `""` |
Expand All @@ -80,7 +80,7 @@ The chart can be customized using the following configurable parameters:
| |
| `pmm.enabled` | Enable integration with [Percona Monitoring and Management software](https://www.percona.com/blog/2020/07/23/using-percona-kubernetes-operators-with-percona-monitoring-and-management/) | `false` |
| `pmm.image.repository` | PMM Container image repository | `percona/pmm-client` |
| `pmm.image.tag` | PMM Container image tag | `2.43.2` |
| `pmm.image.tag` | PMM Container image tag | `2.44.0` |
| `pmm.serverHost` | PMM server related K8S service hostname | `monitoring-service` |
| `pmm.containerSecurityContext` | Set the security context for PMM container | `{}` |
| `pmm.resources` | Set resources for PMM container | `{}` |
Expand Down Expand Up @@ -113,6 +113,8 @@ The chart can be customized using the following configurable parameters:
| `replsets.rs0.runtimeClass` | ReplicaSet Pod runtimeClassName | `""` |
| `replsets.rs0.sidecars` | ReplicaSet Pod sidecars | `{}` |
| `replsets.rs0.sidecarVolumes` | ReplicaSet Pod sidecar volumes | `[]` |
| `replsets.rs0.sidecarVolumes.nfs.server` | The hostname of the NFS server that will provide remote filesystem to the custom sidecar container volume for Replica Set Pods. | `""` |
| `replsets.rs0.sidecarVolumes.nfs.path` | The path on the NFS server that will be provided as a remote filesystem to the custom sidecar container volume for Replica Set Pods. | `""` |
| `replsets.rs0.sidecarPVCs` | ReplicaSet Pod sidecar PVCs | `[]` |
| `replsets.rs0.podDisruptionBudget.maxUnavailable` | ReplicaSet failed Pods maximum quantity | `1` |
| `replsets.rs0.splitHorizons` | External URI for Split-horizon for replica set Pods of the exposed cluster | `{}` |
Expand Down Expand Up @@ -203,6 +205,9 @@ The chart can be customized using the following configurable parameters:
| `sharding.configrs.runtimeClass` | Config ReplicaSet Pod runtimeClassName | `""` |
| `sharding.configrs.sidecars` | Config ReplicaSet Pod sidecars | `{}` |
| `sharding.configrs.sidecarVolumes` | Config ReplicaSet Pod sidecar volumes | `[]` |
| `sharding.configrs.sidecarVolumes.name` | Name of the custom sidecar container volume for Config Server Pods | `""` |
| `sharding.configrs.sidecarVolumes.nfs.server` | The hostname of the NFS server that will provide remote filesystem to the custom sidecar container volume for Config Server Pods | `""` |
| `sharding.configrs.sidecarVolumesnfs.path` | The path on the NFS server that will be provided as a remote filesystem to the custom sidecar container volume for Config Server Pods | `""` |
| `sharding.configrs.sidecarPVCs` | Config ReplicaSet Pod sidecar PVCs | `[]` |
| `sharding.configrs.podDisruptionBudget.maxUnavailable` | Config ReplicaSet failed Pods maximum quantity | `1` |
| `sharding.configrs.expose.enabled` | Allow access to cfg replica from outside of Kubernetes | `false` |
Expand Down Expand Up @@ -288,8 +293,9 @@ The chart can be customized using the following configurable parameters:
| `backup.containerSecurityContext` | Set the security context for a Container | `{}` |
| `backup.restartOnFailure` | Backup Pods restart policy | `true` |
| `backup.image.repository` | PBM Container image repository | `percona/percona-backup-mongodb` |
| `backup.image.tag` | PBM Container image tag | `2.7.0-multi` |
| `backup.image.tag` | PBM Container image tag | `2.8.0-multi` |
| `backup.storages` | Local/remote backup storages settings | `{}` |
| `backup.volumeMounts` | Name of the remote backup storage | `""` |
| `backup.pitr.enabled` | Enable point in time recovery for backup | `false` |
| `backup.pitr.oplogOnly` | Start collecting oplogs even if full logical backup doesn't exist | `false` |
| `backup.pitr.oplogSpanMin` | Number of minutes between the uploads of oplogs | `10` |
Expand Down
2 changes: 2 additions & 0 deletions charts/psmdb-db/templates/cluster.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -650,6 +650,8 @@ spec:
{{- end }}
storages:
{{ .Values.backup.storages | toYaml | indent 6 }}
volumeMounts:
{{ .Values.backup.volumeMounts | toYaml | indent 6 }}
pitr:
{{- if and .Values.backup.enabled .Values.backup.pitr.enabled }}
enabled: true
Expand Down
27 changes: 22 additions & 5 deletions charts/psmdb-db/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ finalizers:
nameOverride: ""
fullnameOverride: ""

crVersion: 1.18.0
crVersion: 1.19.0
pause: false
unmanaged: false
unsafeFlags:
Expand Down Expand Up @@ -50,13 +50,13 @@ upgradeOptions:

image:
repository: percona/percona-server-mongodb
tag: 7.0.14-8-multi
tag: 8.0.4-1-multi

imagePullPolicy: Always
# imagePullSecrets: []
# initImage:
# repository: percona/percona-server-mongodb-operator
# tag: 1.18.0
# tag: 1.19.0
# initContainerSecurityContext: {}
# tls:
# mode: preferTLS
Expand All @@ -72,6 +72,8 @@ secrets: {}
# If not set the operator generates the default secret with name <cluster_name>-secrets
# users: my-cluster-name-secrets
# encryptionKey: my-cluster-name-mongodb-encryption-key
# ssl: my-cluster-name-ssl
# sslInternal: my-cluster-name-ssl-internal
# keyFile: my-cluster-name-mongodb-keyfile
# vault: my-cluster-name-vault
# ldapSecret: my-ldap-secret
Expand All @@ -81,7 +83,7 @@ pmm:
enabled: false
image:
repository: percona/pmm-client
tag: 2.43.2
tag: 2.44.0
serverHost: monitoring-service
# mongodParams: ""
# mongosParams: ""
Expand Down Expand Up @@ -116,6 +118,7 @@ replsets:
# replsetOverrides:
# my-cluster-name-rs0-0:
# host: my-cluster-name-rs0-0.example.net:27017
# priority: 3
# tags:
# key: value-0
# my-cluster-name-rs0-1:
Expand Down Expand Up @@ -194,6 +197,10 @@ replsets:
# - name: sidecar-config
# configMap:
# name: myconfigmap
# - name: backup-nfs
# nfs:
# server: "nfs-service.storage.svc.cluster.local"
# path: "/psmdb-some-name-rs0"
# sidecarPVCs:
# - apiVersion: v1
# kind: PersistentVolumeClaim
Expand Down Expand Up @@ -229,6 +236,7 @@ replsets:
# labels:
# some-label: some-key
# internalTrafficPolicy: Local
# externalTrafficPolicy: Local
# schedulerName: ""
resources:
limits:
Expand Down Expand Up @@ -404,6 +412,7 @@ sharding:
# labels:
# some-label: some-key
# internalTrafficPolicy: Local
# externalTrafficPolicy: Local
resources:
limits:
cpu: "300m"
Expand Down Expand Up @@ -498,6 +507,7 @@ sharding:
# labels:
# some-label: some-key
# internalTrafficPolicy: Local
# externalTrafficPolicy: Local
# nodePort: 32017
# auditLog:
# destination: file
Expand Down Expand Up @@ -567,7 +577,7 @@ backup:
enabled: true
image:
repository: percona/percona-backup-mongodb
tag: 2.7.0-multi
tag: 2.8.0-multi
# annotations:
# iam.amazonaws.com/role: role-arn
# podSecurityContext: {}
Expand Down Expand Up @@ -615,6 +625,13 @@ backup:
# prefix: PREFIX-NAME
# endpointUrl: https://accountName.blob.core.windows.net
# credentialsSecret: SECRET-NAME
# backup-nfs:
# type: filesystem
# filesystem:
# path: /mnt/nfs/
# volumeMounts:
# - mountPath: /mnt/nfs/
# name: backup-nfs
pitr:
enabled: false
oplogOnly: false
Expand Down
8 changes: 4 additions & 4 deletions charts/psmdb-operator/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
apiVersion: v2
appVersion: "1.18.0"
appVersion: "1.19.0"
description: A Helm chart for deploying the Percona Operator for MongoDB
name: psmdb-operator
home: https://docs.percona.com/percona-operator-for-mongodb/
version: 1.18.0
version: 1.19.0
maintainers:
- name: tplavcic
email: [email protected]
- name: nmarukovich
email: [email protected]
- name: spron-in
email: [email protected]
- name: jvpasinatto
email: [email protected]
4 changes: 2 additions & 2 deletions charts/psmdb-operator/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,15 +19,15 @@ To install the chart with the `psmdb` release name using a dedicated namespace (

```sh
helm repo add percona https://percona.github.io/percona-helm-charts/
helm install my-operator percona/psmdb-operator --version 1.18.0 --namespace my-namespace
helm install my-operator percona/psmdb-operator --version 1.19.0 --namespace my-namespace
```

The chart can be customized using the following configurable parameters:

| Parameter | Description | Default |
| ---------------------------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------- |
| `image.repository` | PSMDB Operator Container image name | `percona/percona-server-mongodb-operator` |
| `image.tag` | PSMDB Operator Container image tag | `1.18.0` |
| `image.tag` | PSMDB Operator Container image tag | `1.19.0` |
| `image.pullPolicy` | PSMDB Operator Container pull policy | `Always` |
| `image.pullSecrets` | PSMDB Operator Pod pull secret | `[]` |
| `replicaCount` | PSMDB Operator Pod quantity | `1` |
Expand Down
Loading

0 comments on commit 147d57a

Please sign in to comment.