OCPBUGS#16954: AWS Outposts documentation doesn't reflect the correct support status

[ogradyp]

https://issues.redhat.com/browse/OCPBUGS-16954 AWS Outposts documentation doesn't reflect the correct support status

Applies to OpenShift version : 4.12, 4.13 & 4.14

Preview: Installing a cluster on AWS with remote workers on AWS Outposts

Reporter review completed by @makentenza
Peer review completed by @stesmith

Thank you.

[openshift-ci-robot]

@ogradyp: This pull request references Jira Issue OCPBUGS-16954, which is invalid:

• expected Jira Issue OCPBUGS-16954 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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.

[ocpdocs-previewbot]

🤖 Build preview is available at:
https://67464--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/32722

[makentenza]

LGTM

[StephenJamesSmith]

/lgtm

[sferich888]

/lgtm
/label px-approve

[openshift-ci]

@sferich888: The label(s) /label px-approve cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, peer-review-done, peer-review-in-progress, peer-review-needed, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/lgtm
/label px-approve

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.

[xltian]

lgtm

[makentenza]

@ogradyp please note that this also applies now to 4.14 since the release and documentation is out already

[kalexand-rh]

LGTM.

Since this also applies to 4.14, open a separate PR that targets enterprise-4.14 and link it to this one. Unless @sferich888 objects, the approvals for this PR also apply to the one for 4.14.

[betherly]

/lgtm

[ogradyp]

This PR has received all of the required CM approvals.

[openshift-ci-robot]

@ogradyp: This pull request references Jira Issue OCPBUGS-16954, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
• expected Jira Issue OCPBUGS-16954 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

https://issues.redhat.com/browse/OCPBUGS-16954 AWS Outposts documentation doesn't reflect the correct support status

Applies to OpenShift version : 4.12, 4.13 & 4.14

Preview: Installing a cluster on AWS with remote workers on AWS Outposts

Reporter review completed by @makentenza
Peer review completed by @stesmith

Thank you.

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.

[ogradyp]

/jira refresh

[openshift-ci-robot]

@ogradyp: This pull request references Jira Issue OCPBUGS-16954, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
• expected Jira Issue OCPBUGS-16954 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[openshift-ci-robot]

@ogradyp: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

https://issues.redhat.com/browse/OCPBUGS # 16954 AWS Outposts documentation doesn't reflect the correct support status

Applies to OpenShift version : 4.12, 4.13 & 4.14

Preview: Installing a cluster on AWS with remote workers on AWS Outposts

Reporter review completed by @makentenza
Peer review completed by @stesmith

Thank you.

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.

[dfitzmau]

Hi @ogradyp .

QE review: QE has approved this change.

Section is missing from the description box of this PR.

Should the AWS Outpost feature be added to the installation TP table in the release notes for 4.14, 4.13, and 4.12? This would provide better visibility of the feature in a commonly referenced source for checking support statuses of features.

[ogradyp]

Hi @ogradyp .

QE review: QE has approved this change.

Section is missing from the description box of this PR.

Should the AWS Outpost feature be added to the installation TP table in the release notes for 4.14, 4.13, and 4.12? This would provide better visibility of the feature in a commonly referenced source for checking support statuses of features.

Hi @dfitzmau

Apologies for the delay.

The topic itself, which is the most critical information when it comes to the installation, did not include the TP note, see here
https://docs.openshift.com/container-platform/4.12/installing/installing_aws/installing-aws-outposts-remote-workers.html

This PR now rectifies that at the top of the topic, for 4.12, 4.13, and 41., see here
https://67464--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-outposts-remote-workers

The Release Notes / Installation Technology Preview features table in 4.12 also included this information, see here
https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html#ocp-4-12-technology-preview

Thanks
Padraig

[dfitzmau]

Hi @ogradyp .

QE review: QE has approved this change.

Section is missing from the description box of this PR.
Should the AWS Outpost feature be added to the installation TP table in the release notes for 4.14, 4.13, and 4.12? This would provide better visibility of the feature in a commonly referenced source for checking support statuses of features.

Hi @dfitzmau

Apologies for the delay.

The topic itself, which is the most critical information when it comes to the installation, did not include the TP note, see here https://docs.openshift.com/container-platform/4.12/installing/installing_aws/installing-aws-outposts-remote-workers.html

This PR now rectifies that at the top of the topic, for 4.12, 4.13, and 41., see here https://67464--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-outposts-remote-workers

The Release Notes / Installation Technology Preview features table in 4.12 also included this information, see here https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html#ocp-4-12-technology-preview

Thanks Padraig

Thanks for the reply. I see the entry in the 4.12 release notes, but the 4.13 + release note docs should also have AWS Outpost Platform in the TP table listed? Feature is still TP for 4.13 and 4.14?

[ogradyp]

Hi @ogradyp .

QE review: QE has approved this change.

Section is missing from the description box of this PR.
Should the AWS Outpost feature be added to the installation TP table in the release notes for 4.14, 4.13, and 4.12? This would provide better visibility of the feature in a commonly referenced source for checking support statuses of features.

Hi @dfitzmau
Apologies for the delay.
The topic itself, which is the most critical information when it comes to the installation, did not include the TP note, see here https://docs.openshift.com/container-platform/4.12/installing/installing_aws/installing-aws-outposts-remote-workers.html
This PR now rectifies that at the top of the topic, for 4.12, 4.13, and 41., see here https://67464--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-outposts-remote-workers
The Release Notes / Installation Technology Preview features table in 4.12 also included this information, see here https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html#ocp-4-12-technology-preview
Thanks Padraig

Thanks for the reply. I see the entry in the 4.12 release notes, but the 4.13 + release note docs should also have AWS Outpost Platform in the TP table listed? Feature is still TP for 4.13 and 4.14?

Yes, the feature is still TP for 4.13 and 4.14.

[dfitzmau]

Hi @ogradyp .

QE review: QE has approved this change.

Section is missing from the description box of this PR.
Should the AWS Outpost feature be added to the installation TP table in the release notes for 4.14, 4.13, and 4.12? This would provide better visibility of the feature in a commonly referenced source for checking support statuses of features.

Hi @dfitzmau
Apologies for the delay.
The topic itself, which is the most critical information when it comes to the installation, did not include the TP note, see here https://docs.openshift.com/container-platform/4.12/installing/installing_aws/installing-aws-outposts-remote-workers.html
This PR now rectifies that at the top of the topic, for 4.12, 4.13, and 41., see here https://67464--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-outposts-remote-workers
The Release Notes / Installation Technology Preview features table in 4.12 also included this information, see here https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html#ocp-4-12-technology-preview
Thanks Padraig

Thanks for the reply. I see the entry in the 4.12 release notes, but the 4.13 + release note docs should also have AWS Outpost Platform in the TP table listed? Feature is still TP for 4.13 and 4.14?

Yes, the feature is still TP for 4.13 and 4.14.

Great. Will you be creating separate PRs to update the 4.13 and 4.14 TP tables in the respective release notes docs?

[ogradyp]

Hi @ogradyp .

QE review: QE has approved this change.

Section is missing from the description box of this PR.
Should the AWS Outpost feature be added to the installation TP table in the release notes for 4.14, 4.13, and 4.12? This would provide better visibility of the feature in a commonly referenced source for checking support statuses of features.

Hi @dfitzmau
Apologies for the delay.
The topic itself, which is the most critical information when it comes to the installation, did not include the TP note, see here https://docs.openshift.com/container-platform/4.12/installing/installing_aws/installing-aws-outposts-remote-workers.html
This PR now rectifies that at the top of the topic, for 4.12, 4.13, and 41., see here https://67464--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-outposts-remote-workers
The Release Notes / Installation Technology Preview features table in 4.12 also included this information, see here https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html#ocp-4-12-technology-preview
Thanks Padraig

Thanks for the reply. I see the entry in the 4.12 release notes, but the 4.13 + release note docs should also have AWS Outpost Platform in the TP table listed? Feature is still TP for 4.13 and 4.14?

Yes, the feature is still TP for 4.13 and 4.14.

Great. Will you be creating separate PRs to update the 4.13 and 4.14 TP tables in the respective release notes docs?

This PR is created in 4.13, deals with the update to the install module, and needs to be cherrypicked to 4.12 and 4.14.

The cleanest way to deal with the update to the RN TP table is 2 separate PRs - 1 for 4.13, 1 for 4.14.

[dfitzmau]

Thanks, @ogradyp . Yes, creating seprate PRs to update the TP tables in 4.13 and 4.14 sounds good to me.

/remove-label peer-review-in-progress

/label peer-review-done

[ogradyp]

Thanks, @ogradyp . Yes, creating seprate PRs to update the TP tables in 4.13 and 4.14 sounds good to me.

/remove-label peer-review-in-progress

/label peer-review-done

Thanks for your review @dfitzmau of this PR.

I have also added you as reviewer of these two separate PRs:
TP table for 4.14 #69625
TP table for 4.13 #69617

Many Thanks
Padraig

[dfitzmau]

/label merge-review-needed

[mburke5678]

@ogradyp As I understand, we are supposed to CP from main only, and not between branches. I can merge this to 4.13. But, can you add the TP note to 4.14 through your 4.14 release note PR and pull a new PR for 4.12?

[ogradyp]

@ogradyp As I understand, we are supposed to CP from main only, and not between branches. I can merge this to 4.13. But, can you add the TP note to 4.14 through your 4.14 release note PR and pull a new PR for 4.12?

Thanks @mburke5678 for your review.

As requested please see :

• The TP snippet added to the PR for the 414 RN content here OCPBUGS-16954-RN414: Updated Installation Technology Preview tracker table with AWS Outpost platform entry #69625
• The TP snippet added to a new PR for the 412 content here OCPBUGS-16954-TP412: AWS Outposts documentation doesn't reflect the correct support status #69683