Netobserv API doc regeneration

[skrthomas]

Version(s):

Merge to only the no-1.6 branch - no cherrypicks are required.
This PR is part of an experiment for simplifying merges for asynchronous content, and I will open one PR against main to incorporate all of the Network Observability 1.6 content just before its GA
Issue:

Link to docs preview:

https://76593--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/flowcollector-api.html

QE review:

• QE has approved this change.

Additional information:

Notes to peer reviewers:

• There are about 9 (I think) instances of spec...advanced.scheduling that contain the same specs for tolerations, priorityClassName, nodeSelector, and affinity. After you look at one, feel free to glaze over the others :)
• There are some minor deprecation updates. If you ctrl+f for "deprecated" you should be able to see those changes.

[ocpdocs-previewbot]

🤖 Mon Jun 10 20:58:46 - Prow CI generated the docs preview:

https://76593--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/flowcollector-api.html

[skrthomas]

@memodi @jotak can you PTAL at this PR for API doc regeneration? Joel, I left some review feedback in your PR: netobserv/network-observability-operator#657 (review). So I guess once that's incorporated, I'll copy it over here. It was mostly minor copy edits, things like capitalization and backticks.

[memodi]

looks good overall, just one comment.

[aireilly]

/retest

[kcarmichael08]

I realized that some of the things I commented on were previously accepted text, so I think it's OK to ignore those comments. (I stopped after I realized, about halfway in.) But I think that the link: issue might need to be fixed, just in case it might cause issues in rendering. Also I've been told that blank/empty lines can cause issues, although they seem to be fine in the preview.

[skrthomas]

@kcarmichael08 thanks for the review. I know this is a lot to get through. @jotak do you want to take this feedback upstream with the FlowMetric updates now? Or otherwise, as I said in SCRUM, I can open a Jira to fix these next regeneration.

[jotak]

thanks @kcarmichael08 - almost everything should be addressed upstream in netobserv/network-observability-operator#672 - except a few things which I commented here.

[openshift-ci]

@skrthomas: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[jotak]

thanks @skrthomas !

[memodi]

/label qe-approved