[DOC] Document the steps to expand a PVC
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Document the steps to resize the PVC for database, redis and pulpcore pods.
Describe the solution you'd like
Explain why this is a manual process, provide the steps in case the PVC allows resizing and also for migrating PV, and what should be modified in Pulp CR in case of using a new PVC.
Additional context
Here are some KBs that can be helpful:
- ocp monitoring operator: https://access.redhat.com/solutions/5325711
- migrate pv (in case it is not possible to expand): https://access.redhat.com/solutions/5794841
- resize vsphere vmfs pvc: https://access.redhat.com/solutions/5140131
and also a very good step by step guide from AAP team:
https://issues.redhat.com/browse/AAP-13398?focusedId=22500151&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-22500151
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Red Hat KBs and AAP-13398 guide, then locate the repository's operator documentation for database, Redis, and pulpcore storage. Document why resizing is manual, cover expandable PVCs and PV migration, and explain the Pulp CR changes required when using a new PVC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100