docs: Documentation Maintenance and Content Cleanup for Main and v4.5 Docs#588
Open
balaharish7 wants to merge 1 commit into
Open
docs: Documentation Maintenance and Content Cleanup for Main and v4.5 Docs#588balaharish7 wants to merge 1 commit into
balaharish7 wants to merge 1 commit into
Conversation
… Documentation Signed-off-by: Bala Harish <bala.harish.ac@datacore.com>
balaharish7
requested review from
Abhinandan-Purkait,
niladrih and
tiagolobocastro
|
|
||
|
|
||
| - Run `kubectl get pvc` to fetch the volume name. The volume name looks like: *pvc-ee171da3-07d5-11e8-a5be-42010a8001be*. | ||
| - For each volume, you will notice one I/O controller pod and one or more replicas (as per the storage class configuration). You can use the volume ID (ee171da3-07d5-11e8-a5be-42010a8001be) to view information about the volume and replicas using the [kubectl plugin](../user-guides/replicated-storage-user-guide/replicated-pv-mayastor/advanced-operations/kubectl-plugin.md) |
Member
There was a problem hiding this comment.
This seems to be specific for mayastor
| } | ||
| ``` | ||
|
|
||
| 2. Restart the docker daemon on the nodes. This may cause a temporary disruption of the running containers and cause the node to show up as `Not Ready` until the daemon has restarted successfully. |
Member
There was a problem hiding this comment.
Suggested change
| 2. Restart the docker daemon on the nodes. This may cause a temporary disruption of the running containers and cause the node to show up as `Not Ready` until the daemon has restarted successfully. | |
| 2. Restart the docker daemon on the nodes. This may cause a temporary disruption of the running containers and cause the node to show up as `NotReady` until the daemon has restarted successfully. |
|
|
||
| To resolve this issue, reinstate or recreate the pod to ensure that the volume is properly mounted and recognized by the control plane. | ||
|
|
||
| ### How do I reuse an existing PV - after re-creating Kubernetes StatefulSet and its PVC {#reuse-pv-after-recreating-sts} |
Member
There was a problem hiding this comment.
I don't think this is a FAQ, this makes more sense as a kb type thing, if needed at all
| kubectl get pods -n <namespace> | ||
| ``` | ||
|
|
||
| ### How to prevent container logs from exhausting disk space? {#enable-log-rotation-on-cluster-nodes} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes Completed
Removed obsolete KB articles:
Moved the following KB entries to the FAQ document:
Removed an invalid CNCF hyperlink from the Use Cases document.
Merged duplicate storage recommendation tables and revised the Data Engines Overview content to eliminate redundancy.
Updated the StorageClass parameter table in the Local PV LVM StorageClass Parameters document by consolidating supported values into a simplified format.
Reorganized the StorageClass Parameters document by moving the parameter overview section to the beginning and improving overall content structure.
Simplified the PersistentVolumeClaim conformance matrix in the Local PV LVM Deployment document by consolidating supported parameters and values into a concise reference table.
Added a StorageClass parameter reference table to the Local PV ZFS StorageClass Parameters document to improve readability and navigation.
Removed quorum-related terminology from the Kubernetes Upgrade Best Practices document and updated the guidance to align with Replicated PV Mayastor behavior.
Moved the Kubernetes Upgrade Best Practices document from:
Removed the FAQ entry:
Updated the FAQ:
Performed miscellaneous formatting, alignment, and consistency improvements across multiple documents.