Skip to content

feat: add persistentvolumeclaimretentionpolicy #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lenglet-k
Copy link

@lenglet-k lenglet-k commented May 20, 2025

Summary

Support for opt-in cleanup of PVCs

Link to:

Proof of Work

Create this MongoDBCommunity resource:

--- apiVersion: mongodbcommunity.mongodb.com/v1 kind: MongoDBCommunity metadata: name: mongodb-specify-volumeclaimretention-values spec: members: 3 type: ReplicaSet version: "6.0.5" security: authentication: modes: ["SCRAM"] users: - name: my-user db: admin passwordSecretRef: # a reference to the secret that will be used to generate the user's password name: my-user-password roles: - name: clusterAdmin db: admin - name: userAdminAnyDatabase db: admin scramCredentialsSecretName: my-scram statefulSet: spec: persistentVolumeClaimRetentionPolicy: WhenDeleted: "Delete" WhenScaled: "Delete" template: spec: containers: - name: mongodb-agent readinessProbe: failureThreshold: 50 initialDelaySeconds: 10 # the user credentials will be generated from this secret # once the credentials are generated, this secret is no longer required --- apiVersion: v1 kind: Secret metadata: name: my-user-password type: Opaque stringData: password: <your-password-here>

See pvc created in K8S cluster.

Delete MongoDBCommunity and see pvc disappear.

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you checked for release_note changes?

Reminder (Please remove this when merging)

  • Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
  • Our Short Guide for PRs: Link
  • Remember the following Communication Standards - use comment prefixes for clarity:
    • blocking: Must be addressed before approval.
    • follow-up: Can be addressed in a later PR or ticket.
    • q: Clarifying question.
    • nit: Non-blocking suggestions.
    • note: Side-note, non-actionable. Example: Praise
    • --> no prefix is considered a question
Signed-off-by: lenglet-k <lenglet-k@mgdis.fr>
@lenglet-k lenglet-k requested a review from a team as a code owner May 20, 2025 13:36
@lenglet-k lenglet-k requested review from lsierant and fealebenpae May 20, 2025 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants