OSDOCS#9377: AWS Load Balancer Operator: Content Improvement by xenolinux · Pull Request #70387 · openshift/openshift-docs

xenolinux · 2024-01-17T07:21:58Z

Version(s): 4.12+

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

Link to docs preview: https://70387--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator

QE review:

QE has approved this change.

Additional information:

ocpdocs-previewbot · 2024-01-17T07:29:12Z

🤖 Tue Apr 02 07:47:33 - Prow CI generated the docs preview:
https://70387--ocpdocs-pr.netlify.app

xenolinux · 2024-03-08T10:54:30Z

/label peer-review-needed

opayne1

Sorry again for the late review!! I had just a couple thoughts to consider, but overall looks great! I personally would still get a QE sign off because there are changes to some of the terminology or removes some technical terminology.

opayne1 · 2024-03-12T11:17:02Z

modules/adding-tls-termination.adoc

-<3> The Amazon Resource Name of the certificate that you attach to the load balancer.
-<4> Defines the ingress class name.
+<1> Specifies the Ingress name.
+<2> The controller provisions the load balancer for Ingress in a public subnet to access load balancer over the internet.


Suggested change

<2> The controller provisions the load balancer for Ingress in a public subnet to access load balancer over the internet.

<2> The controller provisions the load balancer for Ingress in a public subnet to access the load balancer over the internet.

I am thinking maybe there should be a "the" before load balancer, but then you have another "the" before internet so I am not sure. Just a thought.

opayne1 · 2024-03-12T11:18:56Z

modules/creating-instance-aws-load-balancer-controller.adoc

-. Create a `service` resource:
+. Create a YAML file that defines the `Service` resource:
 +
+.Example `service-albo.yaml` file


Suggested change

.Example `service-albo.yaml` file

.Example `service-albo.yaml` file:

@opayne1 @xenolinux I don't think we need a colon here, right? This is a heading.

opayne1 · 2024-03-12T11:19:13Z

modules/creating-instance-aws-load-balancer-controller.adoc

-. Deploy an ALB-backed `Ingress` resource:
+. Create a YAML file that defines the `Ingress` resource:
 +
+.Example `ingress-albo.yaml` file


Suggested change

.Example `ingress-albo.yaml` file

.Example `ingress-albo.yaml` file:

@opayne1 @xenolinux I don't think we need a colon here, right? This is a heading.

@mburke5678 That's right. Removed the colon

opayne1 · 2024-03-12T11:20:18Z

modules/creating-instance-aws-load-balancer-controller.adoc

 <1> Defines the ingress resource.
-<2> Specifies the name of the ingress resource.
-<3> Specifies the name of the service resource.
+<2> Specifies the ingress name.


Is Ingress supposed to be capital? I saw some instances where you made the lowercase capital and didn't know if that applies here.

Nice catch! I updated "ingress" instances per https://redhat-documentation.github.io/supplementary-style-guide/#ingress

I'm a little confused. This definition says, and its also my understanding, that when referring to an Ingress resource or the Ingress Controller, it should be capitalized and when describing traffic direction, its lowercase.

opayne1 · 2024-03-12T11:23:35Z

modules/using-aws-cli-create-iam-role-alb-controller.adoc

-. Create an `AWSLoadBalancerController` resource file named `example-sts-iam-role.yaml` with contents such as the following example:
+. Create a YAML file that defines the `AWSLoadBalancerController` object:
 +
+Example `sample-aws-lb-manual-creds.yaml` file


Suggested change

Example `sample-aws-lb-manual-creds.yaml` file

Example `sample-aws-lb-manual-creds.yaml` file:

@opayne1 @xenolinux I don't think we need a colon here, right? This is a heading.

opayne1 · 2024-03-12T11:27:37Z

networking/aws_load_balancer_operator/multiple-ingress-through-single-alb.adoc

 toc::[]

-You can route the traffic to different services that are part of a single domain through a single AWS Load Balancer (ALB). Each Ingress resource provides different endpoints of the domain.
+You can route the traffic to different services that are part of a single domain through a single AWS Load Balancer. Each Ingress provides different endpoints of the domain.


I almost feel like resource should be left in here or add something else like "class" or "instance" because it specifies Ingress. Just a thought.

lihongan · 2024-03-13T07:36:03Z

modules/using-aws-cli-create-iam-role-alb-controller.adoc

 :_mod-docs-content-type: PROCEDURE
 [id="using-aws-cli-create-iam-role-alb-controller_{context}"]
-= Using the AWS CLI to create an IAM role for the Controller
+= Creating an AWS IAM role for the AWS Load Balancer Controller


If change to this, then we have two same subtitle of Creating an AWS IAM role for the AWS Load Balancer Controller

Modified the title

lihongan · 2024-03-13T07:37:08Z

modules/using-ccoctl-create-iam-role-alb-controller.adoc

 :_mod-docs-content-type: PROCEDURE
 [id="using-ccoctl-create-iam-role-alb-controller_{context}"]
-= Using ccoctl to create an IAM role for the Controller
+= Creating an AWS IAM role for the AWS Load Balancer Controller


Here is another same title

Addressed. Modified the title

lihongan · 2024-03-13T08:10:17Z

networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc

+* Using the `ccoctl` binary and a predefined `CredentialsRequest` object.
 * Using the AWS CLI and predefined AWS manifests.

 Use the AWS CLI if your environment does not support the `ccoctl` command.


maybe we could add link to ccoctl utility https://docs.openshift.com/container-platform/4.13/authentication/managing_cloud_provider_credentials/cco-mode-sts.html#cco-ccoctl-configuring_cco-mode-sts

Because in that page we could see the note that only Linux supports ccoctl.

The ccoctl utility is a Linux binary that must run in a Linux environment.

lihongan · 2024-03-13T09:52:52Z

LGTM. thank you!

xenolinux · 2024-04-01T14:53:00Z

/remove-label merge-review-in-progress

mburke5678 · 2024-04-01T16:18:25Z

modules/nw-aws-load-balancer-operator.adoc

 .Procedure

-. You can deploy the AWS Load Balancer Operator on demand from the OperatorHub, by creating a `Subscription` object:
+. You can deploy the AWS Load Balancer Operator on-demand from OperatorHub, by creating a `Subscription` object by running the following command:


Per ISG, on-demand (with hyphen) is an adjective; on demand (no hyphen) is an adverb. Here, on-demand refers to deploy, and is an adverb.

Suggested change

. You can deploy the AWS Load Balancer Operator on-demand from OperatorHub, by creating a `Subscription` object by running the following command:

. You can deploy the AWS Load Balancer Operator on demand from OperatorHub, by creating a `Subscription` object by running the following command:

I'm not sure if the following makes sense, but here is the comparision:

Suggested change

. You can deploy the AWS Load Balancer Operator on-demand from OperatorHub, by creating a `Subscription` object by running the following command:

. You can deploy the on-demand AWS Load Balancer Operator from OperatorHub, by creating a `Subscription` object by running the following command:

ocpdocs-vale-bot · 2024-04-01T16:32:56Z

modules/nw-aws-load-balancer-operator.adoc

 .Procedure

-. You can deploy the AWS Load Balancer Operator on demand from the OperatorHub, by creating a `Subscription` object:
+. You can deploy the AWS Load Balancer Operator on demand from OperatorHub, by creating a `Subscription` object by running the following command:


🤖 [error] RedHat.TermsErrors: Use 'on-demand' rather than 'on demand'.

Seems like this rule might need an update to stop false positives 🤔

mburke5678 · 2024-04-01T17:53:58Z

modules/using-aws-cli-create-iam-role-alb-operator.adoc

+= Creating an AWS IAM role by using the Cloud Credential Operator utility

-You can use the `aws` command line interface to create an IAM role for the AWS Load Balancer (ALB) Operator. The created IAM role is used to interact with subnets and Virtual Private Clouds (VPCs).
+You can use the AWS command line interface to create an IAM role for the AWS Load Balancer Operator. The IAM role is used to interact with subnets and Virtual Private Clouds (VPCs).


Suggested change

You can use the AWS command line interface to create an IAM role for the AWS Load Balancer Operator. The IAM role is used to interact with subnets and Virtual Private Clouds (VPCs).

You can use the AWS Command Line Interface to create an IAM role for the AWS Load Balancer Operator. The IAM role is used to interact with subnets and Virtual Private Clouds (VPCs).

mburke5678 · 2024-04-01T17:54:19Z

modules/using-aws-cli-create-iam-role-alb-operator.adoc

 .Prerequisites

-* You must have access to the `aws` command line interface.
+* You must have access to the AWS command line interface (`aws`).


Suggested change

* You must have access to the AWS command line interface (`aws`).

* You must have access to the AWS Command Line Interface (`aws`).

ocpdocs-vale-bot · 2024-04-02T07:49:20Z

modules/nw-aws-load-balancer-operator.adoc

 .Procedure

-. You can deploy the AWS Load Balancer Operator on demand from the OperatorHub, by creating a `Subscription` object:
+. You can deploy the AWS Load Balancer Operator on demand from OperatorHub, by creating a `Subscription` object by running the following command:


🤖 [error] RedHat.TermsErrors: Use 'on-demand' rather than 'on demand'.

openshift-ci · 2024-04-02T07:49:32Z

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

mburke5678 · 2024-04-02T13:36:34Z

/cherrypick enterprise-4.12

mburke5678 · 2024-04-02T13:36:39Z

/cherrypick enterprise-4.13

mburke5678 · 2024-04-02T13:36:43Z

/cherrypick enterprise-4.14

mburke5678 · 2024-04-02T13:36:46Z

/cherrypick enterprise-4.15

mburke5678 · 2024-04-02T13:36:49Z

/cherrypick enterprise-4.16

openshift-cherrypick-robot · 2024-04-02T13:37:23Z

@mburke5678: #70387 failed to apply on top of branch "enterprise-4.12":

Applying: OSDOCS#9377: AWS Load Balancer Operator: Content Improvement
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	modules/nw-aws-load-balancer-operator.adoc
A	modules/specifying-role-arn-albo-sts.adoc
A	modules/using-aws-cli-create-iam-role-alb-controller.adoc
A	modules/using-aws-cli-create-iam-role-alb-operator.adoc
A	modules/using-ccoctl-create-iam-role-alb-controller.adoc
A	modules/using-ccoctl-create-iam-role-alb-operator.adoc
M	networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc
M	networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator.adoc
Auto-merging networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc
CONFLICT (content): Merge conflict in networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc
CONFLICT (modify/delete): modules/using-ccoctl-create-iam-role-alb-operator.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-ccoctl-create-iam-role-alb-operator.adoc left in tree.
CONFLICT (modify/delete): modules/using-ccoctl-create-iam-role-alb-controller.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-ccoctl-create-iam-role-alb-controller.adoc left in tree.
CONFLICT (modify/delete): modules/using-aws-cli-create-iam-role-alb-operator.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-aws-cli-create-iam-role-alb-operator.adoc left in tree.
CONFLICT (modify/delete): modules/using-aws-cli-create-iam-role-alb-controller.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-aws-cli-create-iam-role-alb-controller.adoc left in tree.
CONFLICT (modify/delete): modules/specifying-role-arn-albo-sts.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/specifying-role-arn-albo-sts.adoc left in tree.
Auto-merging modules/nw-aws-load-balancer-operator.adoc
Auto-merging _topic_maps/_topic_map.yml
CONFLICT (content): Merge conflict in _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OSDOCS#9377: AWS Load Balancer Operator: Content Improvement
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.12

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 · 2024-04-02T13:37:26Z

@mburke5678: #70387 failed to apply on top of branch "enterprise-4.13":

Applying: OSDOCS#9377: AWS Load Balancer Operator: Content Improvement
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	modules/nw-aws-load-balancer-operator.adoc
A	modules/specifying-role-arn-albo-sts.adoc
A	modules/using-aws-cli-create-iam-role-alb-controller.adoc
A	modules/using-aws-cli-create-iam-role-alb-operator.adoc
A	modules/using-ccoctl-create-iam-role-alb-controller.adoc
A	modules/using-ccoctl-create-iam-role-alb-operator.adoc
M	networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc
M	networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator.adoc
Auto-merging networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc
CONFLICT (content): Merge conflict in networking/aws_load_balancer_operator/installing-albo-sts-cluster.adoc
CONFLICT (modify/delete): modules/using-ccoctl-create-iam-role-alb-operator.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-ccoctl-create-iam-role-alb-operator.adoc left in tree.
CONFLICT (modify/delete): modules/using-ccoctl-create-iam-role-alb-controller.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-ccoctl-create-iam-role-alb-controller.adoc left in tree.
CONFLICT (modify/delete): modules/using-aws-cli-create-iam-role-alb-operator.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-aws-cli-create-iam-role-alb-operator.adoc left in tree.
CONFLICT (modify/delete): modules/using-aws-cli-create-iam-role-alb-controller.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/using-aws-cli-create-iam-role-alb-controller.adoc left in tree.
CONFLICT (modify/delete): modules/specifying-role-arn-albo-sts.adoc deleted in HEAD and modified in OSDOCS#9377: AWS Load Balancer Operator: Content Improvement. Version OSDOCS#9377: AWS Load Balancer Operator: Content Improvement of modules/specifying-role-arn-albo-sts.adoc left in tree.
Auto-merging modules/nw-aws-load-balancer-operator.adoc
Auto-merging _topic_maps/_topic_map.yml
CONFLICT (content): Merge conflict in _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OSDOCS#9377: AWS Load Balancer Operator: Content Improvement
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick 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.

openshift-cherrypick-robot · 2024-04-02T13:37:36Z

@mburke5678: new pull request created: #74036

Details

In response to this:

/cherrypick 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 · 2024-04-02T13:37:39Z

@mburke5678: new pull request created: #74037

Details

In response to this:

/cherrypick 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 · 2024-04-02T13:37:44Z

@mburke5678: new pull request created: #74038

Details

In response to this:

/cherrypick 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.

mburke5678 · 2024-04-02T14:26:01Z

@xenolinux Can you PTAL at the 4.12 and 4.13 cherrypicks? There are some significant differences in those branches.

xenolinux changed the title ~~OSDOCS#9377: AWS Load Balancer Operator: Content Improvement~~ [WIP] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement Jan 17, 2024

openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 17, 2024

xenolinux force-pushed the ALBO-improv branch from 60f5fbc to a93b6d7 Compare March 8, 2024 10:32

xenolinux changed the title ~~[WIP] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement~~ OSDOCS#9377: AWS Load Balancer Operator: Content Improvement Mar 8, 2024

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 8, 2024

xenolinux force-pushed the ALBO-improv branch from a93b6d7 to f9f0038 Compare March 8, 2024 10:46

openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Mar 8, 2024

opayne1 added peer-review-in-progress Signifies that the peer review team is reviewing this PR branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Mar 8, 2024

opayne1 added this to the Continuous Release milestone Mar 8, 2024

opayne1 reviewed Mar 12, 2024

View reviewed changes

opayne1 added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Mar 12, 2024

xenolinux force-pushed the ALBO-improv branch 3 times, most recently from cdbd7e3 to 2755673 Compare March 13, 2024 06:52

lihongan reviewed Mar 13, 2024

View reviewed changes

xenolinux force-pushed the ALBO-improv branch from 2755673 to 7e228f8 Compare March 13, 2024 07:52

lihongan reviewed Mar 13, 2024

View reviewed changes

xenolinux force-pushed the ALBO-improv branch 2 times, most recently from b38ba0c to 41fcff0 Compare March 13, 2024 09:42

openshift-ci bot removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Apr 1, 2024

mburke5678 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Apr 1, 2024

mburke5678 reviewed Apr 1, 2024

View reviewed changes

xenolinux force-pushed the ALBO-improv branch from 7ade71e to fc8f1e2 Compare April 1, 2024 16:26

ocpdocs-vale-bot reviewed Apr 1, 2024

View reviewed changes

mburke5678 reviewed Apr 1, 2024

View reviewed changes

OSDOCS#9377: AWS Load Balancer Operator: Content Improvement

eab33d4

xenolinux force-pushed the ALBO-improv branch from fc8f1e2 to eab33d4 Compare April 2, 2024 07:43

ocpdocs-vale-bot reviewed Apr 2, 2024

View reviewed changes

mburke5678 merged commit ba46908 into openshift:main Apr 2, 2024

openshift-cherrypick-robot mentioned this pull request Apr 2, 2024

[enterprise-4.14] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement #74036

Merged

This was referenced Apr 2, 2024

[enterprise-4.15] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement #74037

Merged

[enterprise-4.16] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement #74038

Merged

xenolinux deleted the ALBO-improv branch April 3, 2024 07:09

This was referenced Apr 3, 2024

[enterprise-4.12] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement #74121

Merged

[enterprise-4.13] OSDOCS#9377: AWS Load Balancer Operator: Content Improvement #74122

Merged

	<2> The controller provisions the load balancer for Ingress in a public subnet to access load balancer over the internet.
	<2> The controller provisions the load balancer for Ingress in a public subnet to access the load balancer over the internet.

	.Example `service-albo.yaml` file
	.Example `service-albo.yaml` file:

	.Example `ingress-albo.yaml` file
	.Example `ingress-albo.yaml` file:

	Example `sample-aws-lb-manual-creds.yaml` file
	Example `sample-aws-lb-manual-creds.yaml` file:

	. You can deploy the AWS Load Balancer Operator on-demand from OperatorHub, by creating a `Subscription` object by running the following command:
	. You can deploy the AWS Load Balancer Operator on demand from OperatorHub, by creating a `Subscription` object by running the following command:

	. You can deploy the AWS Load Balancer Operator on-demand from OperatorHub, by creating a `Subscription` object by running the following command:
	. You can deploy the on-demand AWS Load Balancer Operator from OperatorHub, by creating a `Subscription` object by running the following command:

	You can use the AWS command line interface to create an IAM role for the AWS Load Balancer Operator. The IAM role is used to interact with subnets and Virtual Private Clouds (VPCs).
	You can use the AWS Command Line Interface to create an IAM role for the AWS Load Balancer Operator. The IAM role is used to interact with subnets and Virtual Private Clouds (VPCs).

	* You must have access to the AWS command line interface (`aws`).
	* You must have access to the AWS Command Line Interface (`aws`).

Conversation

xenolinux commented Jan 17, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Jan 17, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

xenolinux commented Mar 8, 2024

Uh oh!

opayne1 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!

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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lihongan commented Mar 13, 2024

Uh oh!

xenolinux commented Apr 1, 2024

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!

openshift-ci bot commented Apr 2, 2024

Uh oh!

mburke5678 commented Apr 2, 2024

Uh oh!

mburke5678 commented Apr 2, 2024

Uh oh!

mburke5678 commented Apr 2, 2024

Uh oh!

mburke5678 commented Apr 2, 2024

Uh oh!

mburke5678 commented Apr 2, 2024

Uh oh!

openshift-cherrypick-robot commented Apr 2, 2024

Uh oh!

xenolinux commented Jan 17, 2024 •

edited

Loading

ocpdocs-previewbot commented Jan 17, 2024 •

edited

Loading