Skip to content

OSDOCS-17464: Finalize 4.21 release notes with SME feedback#111595

Open
jseseCCS wants to merge 1 commit into
openshift:enterprise-4.21from
jseseCCS:OSDOCS-17464-helm-ui-fix
Open

OSDOCS-17464: Finalize 4.21 release notes with SME feedback#111595
jseseCCS wants to merge 1 commit into
openshift:enterprise-4.21from
jseseCCS:OSDOCS-17464-helm-ui-fix

Conversation

@jseseCCS

Copy link
Copy Markdown
Contributor

Version(s): 4.21

Issue: OSDOCS-17464

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 13, 2026
@openshift-ci-robot

openshift-ci-robot commented May 13, 2026

Copy link
Copy Markdown

@jseseCCS: This pull request references OSDOCS-17464 which is a valid jira issue.

Details

In response to this:

Version(s): 4.21

Issue: OSDOCS-17464

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 13, 2026
@openshift-ci

openshift-ci Bot commented May 13, 2026

Copy link
Copy Markdown

Hi @jseseCCS. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@jseseCCS

Copy link
Copy Markdown
Contributor Author

to merge reviewer:

This PR replaces #105976.

While reviewing my open PRs, I realized these 4.21 changes hadn't been merged and the previous PR had significantly diverged from the base branch. I'm making it right by opening this fresh PR to ensure 4.21 stays accurate.

@jseseCCS

Copy link
Copy Markdown
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label May 13, 2026
@bergerhoffer

Copy link
Copy Markdown
Contributor

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 14, 2026
@bergerhoffer

Copy link
Copy Markdown
Contributor

@jseseCCS You need to follow the steps to join the openshift org, so you don't keep running into this. I'll send you the link to the source page with instructions over slack.

@ocpdocs-previewbot

Copy link
Copy Markdown

🤖 Thu May 14 15:43:02 - Prow CI generated the docs preview:

https://111595--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-21-release-notes.html

@openshift-ci

openshift-ci Bot commented May 14, 2026

Copy link
Copy Markdown

@jseseCCS: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@ShaunaDiaz ShaunaDiaz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit, but it is a merge blocker

ConsoleLink support for email links::
+
The `ConsoleLink` Custom Resource Definition supports `mailto:` links. You can create email links in the OpenShift web console that open the default email client.
he `ConsoleLink` Custom Resource Definition supports `mailto:` links. The contact email link displays in the **User menu** under the **username** and opens the default email client with the email address prefilled.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
he `ConsoleLink` Custom Resource Definition supports `mailto:` links. The contact email link displays in the **User menu** under the **username** and opens the default email client with the email address prefilled.
The `ConsoleLink` Custom Resource Definition supports `mailto:` links. The contact email link displays in the **User menu** under the **username** and opens the default email client with the email address prefilled.

@ShaunaDiaz ShaunaDiaz removed the merge-review-needed Signifies that the merge review team needs to review this PR label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants