NFS PVC e2e

Open
#1,663 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes
Domain
infrastructure, testing-qa

Research direction

The issue names only an NFS PVC end-to-end task and provides no file, test, or entry point. Start by locating existing PVC and storage e2e coverage in the repository, then clarify the expected NFS scenarios and the checks that define completion.

Written by the indexing model from the issue text.

Description

kind/feature lifecycle/frozen

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Dominant language
Go
Stars
92
Forks
93
Avg merge
1d 23h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openshift/oadp-operator

All issues in openshift/oadp-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.