`odo doctor`: check storage/volume creation

[rm3l]

/kind user-story

User Story

As an odo user, I want to quickly verify that there are no issues that would prevent me from using all odo's features.

odo doctor can be used as a diagnostic command to find potential issues (on my local machine or in my cluster) in advance, and provide helpful information about what needs to be resolved if any issues arise.

Scope: check that odo can create volumes

Acceptance Criteria

• [ ] Check for the default storage class in the cluster, if it wouldn't cause issues with volumes
• [ ] check permission issues
  • [ ] without any FS options
  • [ ] with fsGroup options (https://odo.dev/docs/user-guides/advanced/using-odo-with-other-clusters#set-fsgroup-to-the-podsecuritycontext)
• [ ] For each failing check, it should provide information about possible remediation steps
• [ ] It should provide JSON output
• [ ] Documentation should provide a clear description of each check and the possible remediation steps for each issue

Links

• Related Epic (mandatory):

/kind user-story

[rm3l]

Grooming (Jul 20, 2023)

• Try to create a PVC on the target cluster. If it does not succeed, let the user know what we tried to do, along with some links to documentation
• Test on podman depending on the --platform flag (cluster by default)

[github-actions[bot]]

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

[github-actions[bot]]

This issue was closed because it has been inactive for 30 days since being marked as stale.

[rm3l]

/reopen /remove-lifecycle stale /remove-lifecycle rotten /lifecycle frozen

[openshift-ci[bot]]

@rm3l: Reopened this issue.

In response to this:

/reopen /remove-lifecycle stale /remove-lifecycle rotten /lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.