Closed walterlopatka closed 2 years ago
I'm not sure of this needs any additional documentation. Maybe I should add something to the troubleshooting section of README. Hopefully this tack of using a job to tar the PVC contents, and then kubectl cp to the local host is good enough to satisfy the request.
lgtm
Well it looks good once the Shellcheck error is fixed.
Description
This is a new tool to collect log files from PVC for the case when a Pod is not running and support bundle cannot collect this data otherwise. This is intended to be a support or advanced tool for a special circumstance.
This uses a Kubernetes job to start a Pod that mounts the PVC specified by the user. It tars the contents of the PVC into tmp. The script then kubectl cp's the tar file to the local host.
This script provides basic error checking, but there are some inputs that can cause problems, such as specifying a PVC that does not exist in the specified namespace. In this case the script with hang with the collector pod in "Pending" state. (This is pretty obvious from script stdout.)
Type of change
Applicable issues
CORTX image version requirements
N/A
How was this tested?
Local testing of various cortx PVCs.
Checklist
If this change requires newer CORTX or third party image versions:
image
fields in solution.example.yaml have been updated to use the required versions.appVersion
field of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:
)