Update README to clarify the scope of issues.

[reasonerjt]

Thank you for contributing to Velero!

Please add a summary of your change

Does your change fix a particular issue?

Fixes #(issue)

Please indicate you've done the following:

• Accepted the DCO. Commits without the DCO will delay acceptance.
• Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
• Updated the corresponding documentation in site/content/docs/main.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.58%. Comparing base (5f9c53a) to head (b117963).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7717      +/-   ##
==========================================
- Coverage   58.60%   58.58%   -0.03%     
==========================================
  Files         343      343              
  Lines       28593    28593              
==========================================
- Hits        16757    16751       -6     
- Misses      10418    10423       +5     
- Partials     1418     1419       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kaovilai]

Can you add links for OADP support?

https://access.redhat.com/support/cases/#/troubleshoot/describe-issue?product=OpenShift%20API%20for%20Data%20Protection&version=

Thanks!

[sseago]

Hmm. Maybe a bullet list below the note for specific downstream products with known support ticket URLs would be appropriate here, using the above for OADP, and accepting contribution for other links as appropriate.

[weshayutin]

yes.. IMHO ideally we collect the right link/pointer to popular downstream support of Velero and link them together. In the hope users find the appropriate link and save upstream a bit of time and energy.

[kaovilai]

And another link for FAQ: https://red.ht/oadp-faq

[weshayutin]

@anshulahuja98 @draghuram @ihcsim @Frank51 WDYT? In an attempt to keep downstream bugs out of upstream velero, we were thinking to link to downstream support in the troubleshooting guide. If you agree and have clearance to add a link perhaps post here.

[anshulahuja98]

@anshulahuja98 @draghuram @ihcsim @Frank51 WDYT? In an attempt to keep downstream bugs out of upstream velero, we were thinking to link to downstream support in the troubleshooting guide. If you agree and have clearance to add a link perhaps post here.

Hi
I think overall this makes sense for products which are OSS and using velero (ex. OADP). Where customer is truly aware that velero is the underlying engine and hence they might create issues here.
For our product, it is more of a managed solution, we don't expect customers to create any issues on github(we do not mention/ encourage the route)
Issues flow through MS Support and eventually reach us, then our engineering team follows up in community as required.

So far no customer of our product has created issues directly, and I don't expect that to change in near future.

Having said that, I don't have anything to add in terms of links for now.
We can evaluate in the future again if something changes for us in terms of support.