Skip to content

OSDOCS#12768: Adding docs for OSSO 1.4.0 #89395

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 6, 2025

Conversation

bergerhoffer
Copy link
Contributor

@bergerhoffer bergerhoffer commented Feb 28, 2025

Version(s):
4.18+

Issue:
https://issues.redhat.com/browse/OSDOCS-12768

Link to docs preview:
https://89395--ocpdocs-pr.netlify.app/openshift-enterprise/latest/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.html#secondary-scheduler-operator-release-notes-1.4.0_nodes-secondary-scheduler-release-notes

QE review:

  • QE has approved this change.

Additional information:

Will need to update the advisory link once we get it on the release day - currently scheduled for 9 April.
Advisory link is updated - ready to merge once I get the green light that the release is complete

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 28, 2025
@bergerhoffer bergerhoffer added this to the Continuous Release milestone Feb 28, 2025
@bergerhoffer
Copy link
Contributor Author

@zhouying7780 Can you please QE review?

This is the same known issue and same statement about CVE fixes as we put when there are no other features or changes coming in. For example: https://docs.openshift.com/container-platform/4.15/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.html#secondary-scheduler-operator-release-notes-1.2.2

Note that the advisory link won't work yet - we won't get this link until the release date, so you can ignore that for now.

Preview: https://89395--ocpdocs-pr.netlify.app/openshift-enterprise/latest/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.html#secondary-scheduler-operator-release-notes-1.4.0_nodes-secondary-scheduler-release-notes

@bergerhoffer
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Feb 28, 2025

The following advisory is available for the {secondary-scheduler-operator-full} 1.4.0:

* link:https://access.redhat.com/errata/RH??-2025:TODO[RH??-2025:TODO]

Choose a reason for hiding this comment

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

Is this right : [RH??-2025:TODO](https://access.redhat.com/errata/RH??-2025:TODO)

Copy link
Contributor

Choose a reason for hiding this comment

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

The link to the advisory is not working.

Copy link
Contributor

Choose a reason for hiding this comment

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

@sr1kar99 Links will be available after the operator is shipped. This lgtm.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes what @snarayan-redhat said - that link isn't available until the day of the release. We used to at least know what the link would be ahead of time (it just wouldn't work). But now with Konflux, we don't even know what the link will be until it has shipped live. I will update this on the release date once I have that information.

I opened https://issues.redhat.com/browse/KONFLUX-5287 awhile ago to request a way to get that advisory link in advance.

@sr1kar99
Copy link
Contributor

sr1kar99 commented Mar 3, 2025

/label peer-review-in-progress
/remove-label peer-review-needed

@openshift-ci openshift-ci bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Mar 3, 2025
Copy link
Contributor

@sr1kar99 sr1kar99 left a comment

Choose a reason for hiding this comment

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

/lgtm

Adding @snarayan-redhat for another round of review.


The following advisory is available for the {secondary-scheduler-operator-full} 1.4.0:

* link:https://access.redhat.com/errata/RH??-2025:TODO[RH??-2025:TODO]
Copy link
Contributor

Choose a reason for hiding this comment

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

The link to the advisory is not working.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2025
@snarayan-redhat snarayan-redhat added peer-review-done Signifies that the peer review team has reviewed this PR branch/enterprise-4.19 and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Mar 3, 2025
@snarayan-redhat
Copy link
Contributor

@bergerhoffer Added 4.19 label since it's tagged for 4.18+.

@zhouying7780
Copy link

/lgtm

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 19, 2025
@bergerhoffer
Copy link
Contributor Author

Updated date to show new release date of April 9.

[id="secondary-scheduler-1.4.0-new-features_{context}"]
=== New features and enhancements

* This release of the {secondary-scheduler-operator} updates the Kubernetes version to 1.31.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ingvagabund @zhouying7780 I added this line because we had started noting when these operator versions bumped the kube version. Let me know if this looks okay to you!

Copy link
Member

Choose a reason for hiding this comment

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

This looks great. Simple and informative.

@zhouying7780
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2025
@ingvagabund
Copy link
Member

LGTM

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2025
@zhouying7780
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 30, 2025
Copy link

openshift-ci bot commented Apr 30, 2025

New changes are detected. LGTM label has been removed.

Copy link

openshift-ci bot commented May 6, 2025

@bergerhoffer: 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.

@bergerhoffer bergerhoffer merged commit 43857aa into openshift:main May 6, 2025
2 checks passed
@bergerhoffer
Copy link
Contributor Author

/cherrypick enterprise-4.19

@bergerhoffer
Copy link
Contributor Author

/cherrypick enterprise-4.18

@openshift-cherrypick-robot

@bergerhoffer: new pull request created: #93038

In response to this:

/cherrypick enterprise-4.19

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.

@openshift-cherrypick-robot

@bergerhoffer: new pull request created: #93039

In response to this:

/cherrypick enterprise-4.18

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.18 branch/enterprise-4.19 peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants