Skip to content
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

OSSM-4104: Service Mesh 2.5 Release Notes (2.5 Release) #68434

Merged
merged 1 commit into from Mar 18, 2024

Conversation

rh-tokeefe
Copy link
Contributor

@rh-tokeefe rh-tokeefe commented Nov 27, 2023

PR for Service Mesh 2.5/2.4.6/2.3.10 layered product release. All content for prior releases was previously reviewed and approved. Target date for release March 18.

Version(s): OCP 4.13+

Issue: https://issues.redhat.com/browse/OSSM-4104

Link to docs preview:

https://68434--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes#new-features-red-hat-openshift-service-mesh-version-2-5

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 Nov 27, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 27, 2023

@rh-tokeefe: This pull request references OSSM-4104 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set.

In response to this:

Version(s): OCP 4.12+

Issue: https://issues.redhat.com/browse/OSSM-4104

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.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 27, 2023
@rh-tokeefe rh-tokeefe changed the title OSSM-4104: Service Mesh 2.5 Release Notes [WIP] OSSM-4104: Service Mesh 2.5 Release Notes Nov 27, 2023
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 27, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 27, 2023

@rh-tokeefe: This pull request references OSSM-4104 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set.

In response to this:

Version(s): OCP 4.12+

Issue: https://issues.redhat.com/browse/OSSM-4104

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
Copy link

ocpdocs-previewbot commented Nov 27, 2023

🤖 Mon Mar 18 12:14:05 - Prow CI generated the docs preview:
https://68434--ocpdocs-pr.netlify.app

@rh-tokeefe rh-tokeefe force-pushed the OSSM-4104 branch 2 times, most recently from 170b831 to ef81862 Compare November 27, 2023 21:24
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2023

@rh-tokeefe: This pull request references OSSM-4104 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set.

In response to this:

Version(s): OCP 4.12+

Issue: https://issues.redhat.com/browse/OSSM-4104

Link to docs preview: https://68434--docspreview.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes

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.

@rh-tokeefe rh-tokeefe force-pushed the OSSM-4104 branch 18 times, most recently from ab9a969 to 3090c21 Compare December 5, 2023 18:30
@rh-tokeefe rh-tokeefe force-pushed the OSSM-4104 branch 2 times, most recently from 720ed58 to 09f65d2 Compare December 11, 2023 18:00
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 18, 2024

@rh-tokeefe: This pull request references OSSM-4104 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.16." or "openshift-4.16.", but it targets "OSSM 2.5.0" instead.

In response to this:

** PR for Service Mesh 2.5/2.4.6/2.3.10 layered product release. All content for prior releases was previously reviewed and approved. Target date for release March 18. **

Version(s): OCP 4.13+

Issue: https://issues.redhat.com/browse/OSSM-4104

Link to docs preview:

https://68434--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes#new-features-red-hat-openshift-service-mesh-version-2-5

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-robot
Copy link

openshift-ci-robot commented Mar 18, 2024

@rh-tokeefe: This pull request references OSSM-4104 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.16." or "openshift-4.16.", but it targets "OSSM 2.5.0" instead.

In response to this:

PR for Service Mesh 2.5/2.4.6/2.3.10 layered product release. All content for prior releases was previously reviewed and approved. Target date for release March 18.

Version(s): OCP 4.13+

Issue: https://issues.redhat.com/browse/OSSM-4104

Link to docs preview:

https://68434--ocpdocs-pr.netlify.app/openshift-enterprise/latest/service_mesh/v2x/servicemesh-release-notes#new-features-red-hat-openshift-service-mesh-version-2-5

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.

@rh-tokeefe
Copy link
Contributor Author

Rebased PR March 18

Copy link

openshift-ci bot commented Mar 18, 2024

@rh-tokeefe: 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/test-infra repository. I understand the commands that are listed here.

@rh-tokeefe
Copy link
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 Mar 18, 2024
@rh-tokeefe
Copy link
Contributor Author

rh-tokeefe commented Mar 18, 2024

Just learned the 2.5 code went live. If this looks good after merge review, it is now safe to merge.

@jab-rh jab-rh merged commit 9ba9184 into openshift:main Mar 18, 2024
2 checks passed
@jab-rh
Copy link
Contributor

jab-rh commented Mar 18, 2024

/cherry-pick enterprise-4.16

@jab-rh
Copy link
Contributor

jab-rh commented Mar 18, 2024

/cherry-pick enterprise-4.15

@jab-rh
Copy link
Contributor

jab-rh commented Mar 18, 2024

/cherry-pick enterprise-4.14

@jab-rh
Copy link
Contributor

jab-rh commented Mar 18, 2024

/cherry-pick enterprise-4.13

@openshift-cherrypick-robot

@jab-rh: new pull request created: #73306

In response to this:

/cherry-pick enterprise-4.16

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-cherrypick-robot

@jab-rh: new pull request created: #73307

In response to this:

/cherry-pick enterprise-4.15

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-cherrypick-robot

@jab-rh: new pull request created: #73308

In response to this:

/cherry-pick enterprise-4.14

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-cherrypick-robot

@jab-rh: new pull request created: #73309

In response to this:

/cherry-pick enterprise-4.13

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.

@jab-rh jab-rh removed the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 19, 2024

Support for the Jaeger Operator is deprecated. To collect trace spans, use the {DTProductName} (Tempo) Stack.

Support for the Elastic Search Operator is deprecated.
Copy link
Contributor

Choose a reason for hiding this comment

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

Elastic Search Operator should use the attribute. Elasticsearch is one word.

Copy link
Contributor

@bergerhoffer bergerhoffer left a comment

Choose a reason for hiding this comment

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

LGTM for merging!

@bergerhoffer
Copy link
Contributor

Ignore that, wrong PR :)

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. peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet