Remove Support section from OKD docs

[mburke5678]

Please remove the "Support" section of the OKD Product Docs.

okd-project/working-group#2

[mburke5678]

PR in progress: #58577

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[gabriel-rh]

Based on the topic map, should the "Getting support" page be output at all for OKD?

Name: Support
Dir: support
Distros: openshift-enterprise,openshift-online,openshift-origin
Topics:
- Name: Support overview
  File: index
- Name: Managing your cluster resources
  File: managing-cluster-resources
- Name: Getting support
  File: getting-support
  Distros: openshift-enterprise

I would have thought that the Distros: setting on the File: would override that on the Dir: and as a result, asciibinder should not output this page for OKD but it does...

[gabriel-rh]

/remove-lifecycle rotten

[gabriel-rh]

If you use build_for_portal.py on the OKD distro, it shows that the "getting-started" file is not included in the distro:

$ python3 build_for_portal.py --distro openshift-origin --product "OKD" --version 4.13 --no-upstream-fetch
...
Processing support
ERROR (support/index.adoc): "xref:../support/getting-support.adoc#getting-support[Get support]" appears to try to reference a file not included in the "openshift-origin" distro
Processing web_console

And in the drupal-build master.adoc file that it generates, it does not include getting-support.adoc

= Support
:product-author: Red Hat OpenShift Documentation Team
:product-title: OKD
:product-version: 4.13
:openshift-origin:
:imagesdir: images
:idseparator: -

include::index.adoc[leveloffset=+1]

include::managing-cluster-resources.adoc[leveloffset=+1]
...

So it looks like there is a conflict between how asciibinder implements inheritance in the topic map, and how build_for_portal does it.

Personally, I believe build_for_portal is correct here...

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.