Skip to content

K8SPSMDB-1561 Mount the DB PVC in the PMM3 container#2196

Merged
hors merged 3 commits intopercona:mainfrom
sfoulkes:feature/pmm3-data-db-mounts
Jan 16, 2026
Merged

K8SPSMDB-1561 Mount the DB PVC in the PMM3 container#2196
hors merged 3 commits intopercona:mainfrom
sfoulkes:feature/pmm3-data-db-mounts

Conversation

@sfoulkes
Copy link
Contributor

@sfoulkes sfoulkes commented Jan 14, 2026

K8SPSMDB-1561 Powered by Pull Request Badge

This is necessary to allow the node_exporter running in the pmm-client container to collect metrics on the database's persistent volume. This had been fixed for PMM2 in K8SPSMDB-1297 but that change didn't get picked up when PMM3 support was added to the operator shortly after.

@CLAassistant
Copy link

CLAassistant commented Jan 14, 2026

CLA assistant check
All committers have signed the CLA.

@sfoulkes sfoulkes force-pushed the feature/pmm3-data-db-mounts branch from b71ec56 to e1403d5 Compare January 14, 2026 19:45
egegunes
egegunes previously approved these changes Jan 15, 2026
Copy link
Collaborator

@hors hors left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will have psmdb operator 1.22.0 release in two weeks.

@gkech
Copy link
Contributor

gkech commented Jan 15, 2026

For some reason, we had this fix prepared: #1927, but it was missed through the cracks somehow during the merging process.

Please have a look and update the unit tests accordingly.

Thanks!

@gkech gkech changed the title Mount the DB PVC in the PMM3 container K8SPSMDB-1561 Mount the DB PVC in the PMM3 container Jan 15, 2026
@gkech
Copy link
Contributor

gkech commented Jan 15, 2026

created a jira ticket for this as well: K8SPSMDB-1561

@sfoulkes sfoulkes force-pushed the feature/pmm3-data-db-mounts branch from e1403d5 to d179481 Compare January 15, 2026 16:13
@pull-request-size pull-request-size bot added size/M 30-99 lines and removed size/S 10-29 lines labels Jan 15, 2026
This is necessary to allow the node_exporter running in the pmm-client
container to collect metrics on the database's persistent volume.  This
had been fixed for PMM2 in K8SPSMDB-1297 but that change didn't get
picked up when PMM3 support was added to the operator shortly after.
@sfoulkes sfoulkes force-pushed the feature/pmm3-data-db-mounts branch from d179481 to 69f8ccc Compare January 15, 2026 16:15
@sfoulkes
Copy link
Contributor Author

Thanks for the quick review @gkech and @hors. I've fixed the version and updated the unit test.

@JNKPercona
Copy link
Collaborator

Test Name Result Time
arbiter passed 00:11:15
balancer passed 00:18:45
cross-site-sharded passed 00:18:37
custom-replset-name passed 00:10:27
custom-tls passed 00:16:58
custom-users-roles passed 00:10:30
custom-users-roles-sharded passed 00:11:32
data-at-rest-encryption passed 00:12:54
data-sharded passed 00:22:58
demand-backup passed 00:17:32
demand-backup-eks-credentials-irsa passed 00:00:08
demand-backup-fs passed 00:22:32
demand-backup-if-unhealthy passed 00:11:50
demand-backup-incremental passed 00:49:02
demand-backup-incremental-sharded passed 01:04:26
demand-backup-physical-parallel passed 00:09:16
demand-backup-physical-aws passed 00:12:38
demand-backup-physical-azure passed 00:12:22
demand-backup-physical-gcp-s3 passed 00:12:25
demand-backup-physical-gcp-native passed 00:11:48
demand-backup-physical-minio passed 00:21:24
demand-backup-physical-minio-native passed 00:25:13
demand-backup-physical-sharded-parallel passed 00:11:45
demand-backup-physical-sharded-aws passed 00:19:22
demand-backup-physical-sharded-azure passed 00:18:30
demand-backup-physical-sharded-gcp-native passed 00:18:00
demand-backup-physical-sharded-minio passed 00:18:07
demand-backup-physical-sharded-minio-native passed 00:18:35
demand-backup-sharded passed 00:26:33
disabled-auth passed 00:16:45
expose-sharded passed 00:34:09
finalizer passed 00:10:07
ignore-labels-annotations passed 00:07:31
init-deploy passed 00:13:30
ldap passed 00:09:32
ldap-tls passed 00:13:12
limits passed 00:06:08
liveness passed 00:09:05
mongod-major-upgrade passed 00:11:37
mongod-major-upgrade-sharded passed 00:21:03
monitoring-2-0 passed 00:25:40
monitoring-pmm3 passed 00:28:15
multi-cluster-service passed 00:11:43
multi-storage passed 00:19:10
non-voting-and-hidden passed 00:17:07
one-pod passed 00:08:15
operator-self-healing-chaos passed 00:12:42
pitr passed 00:31:39
pitr-physical passed 01:01:02
pitr-sharded passed 00:20:28
pitr-to-new-cluster passed 00:25:45
pitr-physical-backup-source passed 00:54:17
preinit-updates passed 00:05:38
pvc-resize passed 00:12:55
recover-no-primary passed 00:27:12
replset-overrides passed 00:17:34
replset-remapping passed 00:16:12
replset-remapping-sharded passed 00:17:10
rs-shard-migration passed 00:14:13
scaling passed 00:11:09
scheduled-backup passed 00:17:47
security-context passed 00:06:59
self-healing-chaos passed 00:15:14
service-per-pod passed 00:18:48
serviceless-external-nodes passed 00:07:22
smart-update passed 00:08:14
split-horizon passed 00:13:29
stable-resource-version passed 00:04:40
storage passed 00:07:30
tls-issue-cert-manager passed 00:29:34
unsafe-psa passed 00:07:27
upgrade passed 00:10:15
upgrade-consistency passed 00:08:04
upgrade-consistency-sharded-tls passed 00:55:29
upgrade-sharded passed 00:18:54
upgrade-partial-backup passed 00:15:49
users passed 00:17:52
users-vault passed 00:13:34
version-service passed 00:25:00
Summary Value
Tests Run 79/79
Job Duration 02:42:44
Total Test Time 23:48:49

commit: 42fe61a
image: perconalab/percona-server-mongodb-operator:PR-2196-42fe61aa

@hors hors self-requested a review January 16, 2026 11:56
@hors hors merged commit a91ac1e into percona:main Jan 16, 2026
12 of 14 checks passed
@hors
Copy link
Collaborator

hors commented Jan 16, 2026

@sfoulkes Thank you for your contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants