OSDOCS-17161-1:(CQA) APP-2: Deployments - Attachment2 by tedaveryredhat · Pull Request #117380 · openshift/openshift-docs

tedaveryredhat · 2026-08-05T18:42:29Z

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17161

Link to docs preview:
https://117380--ocpdocs-pr.netlify.app/openshift-dedicated/latest/applications/deployments/route-based-deployment-strategies.html
https://117380--ocpdocs-pr.netlify.app/openshift-enterprise/latest/applications/deployments/route-based-deployment-strategies.html
https://117380--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/applications/deployments/route-based-deployment-strategies.html
https://117380--ocpdocs-pr.netlify.app/openshift-rosa/latest/applications/deployments/route-based-deployment-strategies.html

QE review:
N/A

openshift-ci-robot · 2026-08-05T18:42:33Z

@tedaveryredhat: This pull request references OSDOCS-17161 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17161

Link to docs preview:

QE review:
N/A

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.

ocpdocs-previewbot · 2026-08-05T18:51:02Z

🤖 Thu Aug 06 15:21:35 - Prow CI generated the docs preview:

https://117380--ocpdocs-pr.netlify.app/openshift-dedicated/latest/applications/deployments/route-based-deployment-strategies.html
https://117380--ocpdocs-pr.netlify.app/openshift-enterprise/latest/applications/deployments/route-based-deployment-strategies.html
https://117380--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/applications/deployments/route-based-deployment-strategies.html
https://117380--ocpdocs-pr.netlify.app/openshift-rosa/latest/applications/deployments/route-based-deployment-strategies.html

ocpdocs-vale-bot · 2026-08-05T18:52:18Z

+
+:_mod-docs-content-type: PROCEDURE
+[id="deployments-ab-testing-lb-web_{context}"]
+= Managing weights of an existing route using the web console


🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

openshift-ci · 2026-08-06T16:35:03Z

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

tedaveryredhat · 2026-08-07T20:09:49Z

/label merge-review-needed

lahinson

@tedaveryredhat Thanks for your work on this! Just a few small things to address before this one is merged.

lahinson · 2026-08-13T17:13:02Z


-Deployment strategies provide a way for the application to evolve. Some strategies use `Deployment` objects to make changes that are seen by users of all routes that resolve to the application. Other advanced strategies, such as the ones described in this section, use router features in conjunction with `Deployment` objects to impact specific routes.
+[role="_abstract"]
+To roll out application changes to selected traffic in {product-title}, you can use route-based deployment strategies with the router and `Deployment` objects. These advanced strategies, including blue-green, A/B, and canary, affect specific routes rather than every route that resolves to the application.


Short descriptions must not exceed 300 characters in order to be migrated to DITA successfully.

Suggested change

To roll out application changes to selected traffic in {product-title}, you can use route-based deployment strategies with the router and `Deployment` objects. These advanced strategies, including blue-green, A/B, and canary, affect specific routes rather than every route that resolves to the application.

[role="_abstract"]

To roll out application changes to selected traffic in {product-title}, you can use route-based deployment strategies with the router and `Deployment` objects.

These advanced strategies, including blue-green, A/B, and canary, affect specific routes rather than every route that resolves to the application.

lahinson · 2026-08-13T17:14:14Z

 See
 xref:../../applications/deployments/deployment-strategies.adoc#deployment-strategies[Using deployment strategies]
-for more on the basic strategy types.
+for more on the basic strategy types.:_mod-docs-content-type: PROCEDURE


Not sure why this mod-docs text is here.

lahinson · 2026-08-13T17:18:05Z

+
+:_mod-docs-content-type: PROCEDURE
+[id="deployments-ab-one-service-multi-dc_{context}"]
+= One service, multiple `Deployment` objects


Per the OCP docs guidelines, use a gerund for the title of a procedure: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#writing-procedures

Also, module titles should not be formatted with backticks: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#writing-procedures

Suggested change

= One service, multiple `Deployment` objects

= Create multiple Deployment objects that use one service

lahinson · 2026-08-13T17:25:37Z

+= One service, multiple `Deployment` objects
+
+[role="_abstract"]
+To serve multiple application versions through a single service in {product-title}, you can create multiple `Deployment` objects that share a common label selector. Expose one service for those pods so you can scale or update each shard independently while users reach them through the same route.


Suggested change

To serve multiple application versions through a single service in {product-title}, you can create multiple `Deployment` objects that share a common label selector. Expose one service for those pods so you can scale or update each shard independently while users reach them through the same route.

[role="_abstract]

To serve multiple application versions through a single service in {product-title}, you can create multiple `Deployment` objects that share a common label selector.

Expose one service for those pods so you can scale or update each shard independently while users reach them through the same route.

Short descriptions cannot be longer than 300 characters in order to successfully be migrated to DITA.

lahinson · 2026-08-13T17:31:42Z

+
+[NOTE]
+====
+Not all routers may support multiple or weighted backends.


Suggested change

Not all routers may support multiple or weighted backends.

Not all routers support multiple or weighted backends.

IBM Style warns against the use of "may" in technical content.

lahinson · 2026-08-13T17:35:25Z

+
+:_mod-docs-content-type: PROCEDURE
+[id="deployments-ab-testing-lb-web-new-route_{context}"]
+= Managing weights of an new route using the web console


Suggested change

= Managing weights of an new route using the web console

= Managing weights of a new route by using the web console

lahinson · 2026-08-13T17:36:42Z

+
+:_mod-docs-content-type: PROCEDURE
+[id="deployments-ab-testing-lb-web_{context}"]
+= Managing weights of an existing route using the web console


Suggested change

= Managing weights of an existing route using the web console

= Managing weights of an existing route by using the web console

lahinson · 2026-08-13T17:42:13Z


-Blue-green deployments involve running two versions of an application at the same time and moving traffic from the in-production version (the blue version) to the newer version (the green version). You can use a rolling strategy or switch services in a route.
+[role="_abstract"]
+To switch users from a stable application version to a new one in {product-title}, you can set up a blue-green deployment. Run both versions at once, then point the production route at the new (green) service when you are ready, with the option to switch back to the blue version if needed.


The short description needs to be fewer than 300 characters to be successfully migrated to DITA.

Suggested change

To switch users from a stable application version to a new one in {product-title}, you can set up a blue-green deployment. Run both versions at once, then point the production route at the new (green) service when you are ready, with the option to switch back to the blue version if needed.

[role="_abstract"]

To switch users from a stable application version to a new one in {product-title}, you can set up a blue-green deployment.

Run both versions at once, then point the production route at the new (green) service when you are ready, with the option to switch back to the blue version if needed.

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

openshift-ci Bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Aug 5, 2026

ocpdocs-vale-bot reviewed Aug 5, 2026

View reviewed changes

OSDOCS-17161-1:(CQA) APP-2: Deployments - Attachment2

02a3b84

tedaveryredhat force-pushed the OSDOCS-17161-1 branch from fe45c6d to 02a3b84 Compare August 6, 2026 15:07

openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 6, 2026

openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Aug 7, 2026

lahinson added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Aug 13, 2026

lahinson reviewed Aug 13, 2026

View reviewed changes

lahinson added branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 branch/enterprise-5.0 and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR labels Aug 13, 2026

lahinson added this to the Continuous Release milestone Aug 13, 2026

	= One service, multiple `Deployment` objects
	= Create multiple Deployment objects that use one service

	Not all routers may support multiple or weighted backends.
	Not all routers support multiple or weighted backends.

	= Managing weights of an new route using the web console
	= Managing weights of a new route by using the web console

	= Managing weights of an existing route using the web console
	= Managing weights of an existing route by using the web console

Uh oh!

Conversation

tedaveryredhat commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 5, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented Aug 6, 2026

Uh oh!

tedaveryredhat commented Aug 7, 2026

Uh oh!

lahinson left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

tedaveryredhat commented Aug 5, 2026 •

edited

Loading

openshift-ci-robot commented Aug 5, 2026 •

edited by openshift-ci Bot

Loading

ocpdocs-previewbot commented Aug 5, 2026 •

edited

Loading