OSDOCS#10947: Support for CCO in HCP by xenolinux · Pull Request #77653 · openshift/openshift-docs

xenolinux · 2024-06-18T14:06:04Z

Version(s): 4.15+

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

Link to docs preview:

QE review:

QE has approved this change.

SME review:

SME has approved this change.

Additional information:

ocpdocs-previewbot · 2024-06-18T14:16:22Z

🤖 Mon Aug 26 11:57:59 - Prow CI generated the docs preview:

https://77653--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hosted_control_planes/hcp-authentication-authorization.html
https://77653--ocpdocs-pr.netlify.app/openshift-enterprise/latest/operators/operator_sdk/token_auth/osdk-cco-aws-sts.html

jeana-redhat

Nice work navigating the STS conditional spaghetti 😅 I've made a few suggestions here to catch a couple loose ends and match the structure of this in the OCP install books (since that's a clear workflow). I'll catch up with you on Slack about placement considerations for this content 🤓

jeana-redhat · 2024-06-27T13:04:42Z

+[role="_additional-resources"]
+.Additional resources
+
+* To know about the Cloud Credential Operator, see xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator].


Add'l resources should just have the link text :)

Suggested change

* To know about the Cloud Credential Operator, see xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator].

* xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator]

jeana-redhat · 2024-06-27T13:04:45Z


 * To know more about supported identity providers, see xref:../authentication/understanding-identity-provider.adoc#understanding-identity-provider["Understanding identity provider configuration"] in _Authentication and authorization_.
+
+include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]


Might consider bumping this to a +2? Right now it looks like it's part of "Configuring the OAuth server", but IIUC it's not really part of that

Suggested change

include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]

include::modules/cco-ccoctl-configuring.adoc[leveloffset=+2]

Alternatively, you could make a subheading at the == level to put all the CCO stuff inside to more closely match the structure of these tasks in the install books.

So, something like:

Configuring the OAuth server for a hosted cluster by using the CLI

Configuring the OAuth server for a hosted cluster by using the web console

Configuring an {hcp} cluster to use the AWS Security Token Service

Configuring the Cloud Credential Operator utility

Creating AWS resources with the Cloud Credential Operator utility

Creating AWS resources with a single command

Creating AWS resources individually

Incorporating the Cloud Credential Operator utility manifests

This was a bit harder to show with a PR review diff, but I sketched it out in my editor here if you want to see what I'm thinking 🙂

Local render TOC looks like this:

jeana-redhat · 2024-06-27T13:19:23Z

+
+include::modules/cco-ccoctl-install-creating-manifests.adoc[leveloffset=+3]
+
+include::modules/cco-mode-sts.adoc[leveloffset=+1]


this doesn't seem to exist

jeana-redhat · 2024-06-27T13:29:14Z

in addition to this one, the module cco-ccoctl-creating-individually.adoc needs to have an hcp-cco condition included anywhere there's aws-sts for it to render right (assuming all STS steps apply to HCP 🙂)

jeana-redhat · 2024-06-27T13:32:58Z

+* You can use the `ccoctl aws create-all` command to create the AWS resources automatically. This is the quickest way to create the resources. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-at-once_installing-aws-network-customizations[Creating AWS resources with a single command].
+
+* If you need to review the JSON files that the `ccoctl` tool creates before modifying AWS resources, or if the process the `ccoctl` tool uses to create AWS resources automatically does not meet the requirements of your organization, you can create the AWS resources individually. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-individually_installing-aws-network-customizations[Creating AWS resources individually].


For the links in these items, you probably want to point them to the instance of these modules on this page rather than off in IPI install

Suggested change

* You can use the `ccoctl aws create-all` command to create the AWS resources automatically. This is the quickest way to create the resources. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-at-once_installing-aws-network-customizations[Creating AWS resources with a single command].

* If you need to review the JSON files that the `ccoctl` tool creates before modifying AWS resources, or if the process the `ccoctl` tool uses to create AWS resources automatically does not meet the requirements of your organization, you can create the AWS resources individually. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-individually_installing-aws-network-customizations[Creating AWS resources individually].

* You can use the `ccoctl aws create-all` command to create the AWS resources automatically. This is the quickest way to create the resources. See xref:../hosted_control_planes/hcp-authentication-authorization.adoc#cco-ccoctl-creating-at-once_hcp-authentication-authorization[Creating AWS resources with a single command].

* If you need to review the JSON files that the `ccoctl` tool creates before modifying AWS resources, or if the process the `ccoctl` tool uses to create AWS resources automatically does not meet the requirements of your organization, you can create the AWS resources individually. See xref:../hosted_control_planes/hcp-authentication-authorization.adoc#cco-ccoctl-creating-individually_hcp-authentication-authorization[Creating AWS resources individually].

jeana-redhat · 2024-06-27T13:33:32Z

+include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]
+
+[id="hcp-sts-mode-ccoctl_{context}"]
+== Using Credential Operator utility for {hcp}


Suggested change

== Using Credential Operator utility for {hcp}

== Creating {aws-short} resources with the Cloud Credential Operator utility

zanetworker · 2024-07-02T08:47:25Z

looks good. Thanks @xenolinux

huangmingxia · 2024-07-03T07:37:05Z

Hi @xenolinux Please hold off on merging this documentation PR for now. I’ve just reviewed the current doc and noticed that some issues are not clearly explained. I am in the process of reviewing it and will add my comments once I’m finished.
Thank you!

xenolinux · 2024-07-03T08:07:58Z

@huangmingxia Sure. Thanks.

huangmingxia

As @jeana-redhat suggested, the document structure is now very clear.

However, there are differences in how the Cloud Credential Operator works for HyperShift compared to OpenShift:

For HyperShift on AWS, the CCO only supports Manual mode.
In OpenShift, when creating a cluster in Manual mode, ccoctl is typically used to generate manifests and OIDC resources. However, this is not the case for HyperShift. HyperShift Hosted Clusters on AWS are always set to Manual mode by default, and there's no need to use ccoctl to generate manifests or OIDC resources.

For HyperShift, since the CCO only supports AWS in Manual mode and doesn’t require ccoctl to create other resources, given these points, there’s no need to include ccoctl usage in the document, we can remove that section from the doc.

Based on above background, we need to update the following content:

Remove these sections(HyperShift Hosted Clusters on AWS do not use ccoctl. If ccoctl is needed in the future, we can add it then.).

Configuring the Cloud Credential Operator utility
Creating AWS resources with the Cloud Credential Operator utility
Incorporating the Cloud Credential Operator utility manifests

Clarify the steps for creating a Hosted Cluster in Manual mode:
Follow the same steps as in the hcp-getting-started-aws guide.
Add below verification steps after installation:

Verify Hosted Cluster in Manual Mode, check that the Cloud Credential Operator is set to Manual mode by running:
$oc get cloudcredentials cluster -o=jsonpath={.spec.credentialsMode}
The output should be Manual:
Manual
Verify Service Account Issuer is not empty, ensure the serviceAccountIssuer is not empty by executing:
$oc get authentication cluster -o jsonpath --template '{.spec.serviceAccountIssuer }'
The output like:
https://aos-hypershift-ci-oidc-26499.s3.us-east-2.amazonaws.com/hypershift-ci-26499

huangmingxia · 2024-07-05T06:47:06Z

+
+You can configure the Cloud Credential Operator (CCO) utility (`ccoctl`) on hosted clusters to assign components IAM roles that provide short-term, limited-privilege security credentials.
+
+To configure the CCO utility for a hosted cluster, your hosted cluster must use the {aws-short} {sts-short}.


Please change the sentence to this note:
Note:
The Cloud Credential Operator (CCO) currently supports only Manual mode for Hosted Clusters on AWS. All Hosted Clusters are automatically configured to Manual mode by default, regardless of the management cluster's mode. At present, there is no need to generate additional resources using ccoctl.
In the future, if there are scenarios where ccoctl is added, we can update accordingly.

For my education: are hosted clusters using AWS STS, or just manual CCO by itself? I ask because I wasn't aware that we could have AWS STS without the ccoctl 🙂

Let me try to explain in my comment next.

huangmingxia · 2024-07-05T07:04:38Z

@jianping-shu @heliubj18 @YuLi517 Just want you to know this specific change.
@jianping-shu @heliubj18 Please also help review this change when you have time, if you have any questions or other suggestions, please feel free to raise them here. Thanks.

xenolinux · 2024-07-11T12:45:52Z

@huangmingxia I appreciate your review. Thank you!!

I updated this PR as per your suggestions. Can you please re-review?

3. Add below verification steps after installation:
* Verify Hosted Cluster in Manual Mode, check that the Cloud Credential Operator is set to Manual mode by running:
  $oc get cloudcredentials cluster -o=jsonpath={.spec.credentialsMode}
  The output should be Manual:
  Manual

In this command (and the next command) cluster is the hosted cluster name, right? I updated this command as oc get cloudcredentials <hosted_cluster_name> -n <hosted_cluster_namespace> -o=jsonpath={.spec.credentialsMode} -- Please let me know if it needs to be corrected.

* Verify Service Account Issuer is not empty, ensure the `serviceAccountIssuer` is not empty by executing:
  $oc get authentication cluster -o jsonpath --template '{.spec.serviceAccountIssuer }'
  The output like:
  https://aos-hypershift-ci-oidc-26499.s3.us-east-2.amazonaws.com/hypershift-ci-26499

This link https://aos-hypershift-ci-oidc-26499.s3.us-east-2.amazonaws.com/hypershift-ci-26499 is giving the [1] output. Is it the expected output? If not, can you please help with the expected command output?

[1]

<Message>The specified bucket does not exist</Message>
<BucketName>aos-hypershift-ci-oidc-26499</BucketName>
<RequestId>3H472PZ2T22NS3Q9</RequestId>
<HostId>
9I0VrG2h+ZOYvFZMvwsv88WYSbEr+/HTvEpP3p8cuDF+CvXCQKYw/3Tk54cIQ0mqG9HTQd2JWq3BUALblTlR5+M/JWzScfTnhj8Yv/lEW5k=

huangmingxia · 2024-07-11T13:16:47Z

Hi @xenolinux Thank you for the update! I am working on some blocker tasks today and expect to have time to review either tomorrow or next Monday. I will address all the issues you mentioned during my review.
By the way, could you please share the docs preview link again? (It looks like the link is invalid.) Thanks. If you have any other questions, feel free to contact me.

xenolinux · 2024-07-11T13:22:50Z

Hi @xenolinux Thank you for the update! I am working on some blocker tasks today and expect to have time to review either tomorrow or next Monday. I will address all the issues you mentioned during my review. By the way, could you please share the docs preview link again? (It looks like the link is invalid.) Thanks. If you have any other questions, feel free to contact me.

@huangmingxia Sure. No rush. :) Thanks!

It takes a couple of mins to get the preview updated again. Here's the updated preview link to the particular sections:

jianping-shu · 2024-07-15T03:22:46Z

Sorry for late review and feedback!
I'd like to add some background firstly. Let's assume that cloud is aws for next.
Hypershift hosted cluster only supports STS , and its management cluster can be non-STS with CCO running as normal.
Previously Hypershift hosted cluster is created by Hypershift operator without utilizing ccoctl, all logic is done by Hypershift own. There's no CCO running on the hosted cluster.
Feature OCPSTRAT-171 introduced a function that add awsSTSIAMRoleARN in CredentialsRequest file and CCO will generate its corresponding credential secret automatically. To implement the similar feature for the hosted cluster, that's OCPSTRAT-110 which the current doc PR is tied up to.
With OCPSTRAT-110, CCO is running on control plane for the hosted cluster and CCO mode is hard code to Manual.
My comment:
To address OCPSTRAT-110 feature usage, it is better to have a link to the procedure of Add token auth via CCO for Operator authors (AWS STS), introduced by the following PR. I don't know if any difference to add operator for ocp and hosted clusters, I assume the procedures are the same or very close.
#64808

xenolinux · 2024-08-16T09:18:01Z

/label peer-review-needed

lahinson

Looks great! I had a couple suggestions for your consideration, but overall, LGTM.

lahinson · 2024-08-16T13:05:47Z

 * To know more about supported identity providers, see xref:../authentication/understanding-identity-provider.adoc#understanding-identity-provider["Understanding identity provider configuration"] in _Authentication and authorization_.
+
+[id="hcp-cco-aws-sts_{context}"]
+== Using the CCO in a hosted cluster on {aws-short}


Suggested change

== Using the CCO in a hosted cluster on {aws-short}

== Assigning components IAM roles by using the CCO in a hosted cluster on {aws-short}

Just a thought. Is the goal of this task to use the CCO in a hosted cluster, or is it to assign components IAM roles by using the CCO in a hosted cluster?

As per the text Assigning components IAM... fits better. Addressed the suggestion.

lahinson · 2024-08-16T13:07:17Z

+
+[NOTE]
+====
+The CCO only supports a manual mode for hosted clusters on {aws-short}. By default, hosted clusters are configured in a manual mode. The management cluster might use modes other than manual.


Suggested change

The CCO only supports a manual mode for hosted clusters on {aws-short}. By default, hosted clusters are configured in a manual mode. The management cluster might use modes other than manual.

The CCO supports a manual mode only for hosted clusters on {aws-short}. By default, hosted clusters are configured in a manual mode. The management cluster might use modes other than manual.

I think "only" is modifying "a manual mode", so I moved "only" closer to that phrase. If "only" is actually modifying "supports", feel free to ignore this suggestion :)

Ack'ed. Addressed

lahinson · 2024-08-16T13:07:37Z

+[id="hcp-cco-verify-aws-sts_{context}"]
+= Verifying the CCO installation in a hosted cluster on {aws-short}
+
+You can verify if the Cloud Credential Operator (CCO) is running correctly in your hosted control plane.


Suggested change

You can verify if the Cloud Credential Operator (CCO) is running correctly in your hosted control plane.

You can verify that the Cloud Credential Operator (CCO) is running correctly in your hosted control plane.

lahinson · 2024-08-16T13:09:12Z

+[role="_additional-resources"]
+.Additional resources
+
+* xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator].


Suggested change

* xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator].

* xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator]

openshift-ci · 2024-08-26T11:59:14Z

@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-sigs/prow repository. I understand the commands that are listed here.

xenolinux · 2024-08-26T12:14:23Z

/label merge-review-needed

kcarmichael08 · 2024-08-26T18:45:50Z

/cherrypick enterprise-4.15

kcarmichael08 · 2024-08-26T18:46:00Z

/cherrypick enterprise-4.16

kcarmichael08 · 2024-08-26T18:46:11Z

/cherrypick enterprise-4.17

openshift-cherrypick-robot · 2024-08-26T18:46:40Z

@kcarmichael08: new pull request created: #80906

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-sigs/prow repository.

openshift-cherrypick-robot · 2024-08-26T18:46:48Z

@kcarmichael08: new pull request created: #80907

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-sigs/prow repository.

openshift-cherrypick-robot · 2024-08-26T18:46:59Z

@kcarmichael08: new pull request created: #80908

Details

In response to this:

/cherrypick enterprise-4.17

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-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 18, 2024

jeana-redhat reviewed Jun 27, 2024

View reviewed changes

xenolinux force-pushed the cco-hcp branch 2 times, most recently from 4389f5a to 218c9e9 Compare June 27, 2024 14:06

xenolinux changed the title ~~HCP CCO~~ OSDOCS#10947: HCP CCO Jun 27, 2024

xenolinux changed the title ~~OSDOCS#10947: HCP CCO~~ OSDOCS#10947: Support for CCO in HCP Jun 27, 2024

xenolinux force-pushed the cco-hcp branch from 218c9e9 to 2c61669 Compare July 1, 2024 10:34

stevekuznetsov approved these changes Jul 2, 2024

View reviewed changes

huangmingxia suggested changes Jul 5, 2024

View reviewed changes

xenolinux force-pushed the cco-hcp branch 2 times, most recently from 65c6af1 to 3a20f6c Compare July 11, 2024 12:05

openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 11, 2024

xenolinux force-pushed the cco-hcp branch 2 times, most recently from d417263 to 4cb0476 Compare July 11, 2024 12:11

xenolinux force-pushed the cco-hcp branch 2 times, most recently from 3f37009 to 2cc4d84 Compare July 22, 2024 06:53

openshift-ci Bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Aug 16, 2024

lahinson 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 Aug 16, 2024

lahinson reviewed Aug 16, 2024

View reviewed changes

lahinson 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 Aug 16, 2024

xenolinux force-pushed the cco-hcp branch from cf02fe2 to de8aa27 Compare August 26, 2024 11:06

CCO support in HCP on AWS

f028ef8

xenolinux force-pushed the cco-hcp branch from de8aa27 to f028ef8 Compare August 26, 2024 11:49

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

kcarmichael08 added merge-review-in-progress Signifies that the merge review team is reviewing this PR branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Aug 26, 2024

kcarmichael08 added this to the Continuous Release milestone Aug 26, 2024

kcarmichael08 merged commit dd1a0f3 into openshift:main Aug 26, 2024

openshift-cherrypick-robot mentioned this pull request Aug 26, 2024

[enterprise-4.15] OSDOCS#10947: Support for CCO in HCP #80906

Merged

openshift-cherrypick-robot mentioned this pull request Aug 26, 2024

[enterprise-4.16] OSDOCS#10947: Support for CCO in HCP #80907

Merged

openshift-cherrypick-robot mentioned this pull request Aug 26, 2024

[enterprise-4.17] OSDOCS#10947: Support for CCO in HCP #80908

Merged

kcarmichael08 removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Aug 26, 2024

	* To know about the Cloud Credential Operator, see xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator].
	* xref:../operators/operator-reference.adoc#cloud-credential-operator_cluster-operators-ref[Cluster Operators reference page for the Cloud Credential Operator]


		* To know more about supported identity providers, see xref:../authentication/understanding-identity-provider.adoc#understanding-identity-provider["Understanding identity provider configuration"] in _Authentication and authorization_.

		include::modules/cco-ccoctl-configuring.adoc[leveloffset=+3]


		include::modules/cco-ccoctl-install-creating-manifests.adoc[leveloffset=+3]

		include::modules/cco-mode-sts.adoc[leveloffset=+1]

		* You can use the `ccoctl aws create-all` command to create the AWS resources automatically. This is the quickest way to create the resources. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-at-once_installing-aws-network-customizations[Creating AWS resources with a single command].

		* If you need to review the JSON files that the `ccoctl` tool creates before modifying AWS resources, or if the process the `ccoctl` tool uses to create AWS resources automatically does not meet the requirements of your organization, you can create the AWS resources individually. See xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#cco-ccoctl-creating-individually_installing-aws-network-customizations[Creating AWS resources individually].

	== Using Credential Operator utility for {hcp}
	== Creating {aws-short} resources with the Cloud Credential Operator utility


		You can configure the Cloud Credential Operator (CCO) utility (`ccoctl`) on hosted clusters to assign components IAM roles that provide short-term, limited-privilege security credentials.

		To configure the CCO utility for a hosted cluster, your hosted cluster must use the {aws-short} {sts-short}.

	== Using the CCO in a hosted cluster on {aws-short}
	== Assigning components IAM roles by using the CCO in a hosted cluster on {aws-short}

	The CCO only supports a manual mode for hosted clusters on {aws-short}. By default, hosted clusters are configured in a manual mode. The management cluster might use modes other than manual.
	The CCO supports a manual mode only for hosted clusters on {aws-short}. By default, hosted clusters are configured in a manual mode. The management cluster might use modes other than manual.

	You can verify if the Cloud Credential Operator (CCO) is running correctly in your hosted control plane.
	You can verify that the Cloud Credential Operator (CCO) is running correctly in your hosted control plane.

Conversation

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

jeana-redhat 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!

zanetworker commented Jul 2, 2024

Uh oh!

huangmingxia commented Jul 3, 2024

Uh oh!

xenolinux commented Jul 3, 2024

Uh oh!

huangmingxia left a comment

Choose a reason for hiding this comment

Uh oh!

huangmingxia Jul 5, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

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!

huangmingxia commented Jul 5, 2024

Uh oh!

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

Uh oh!

Uh oh!

huangmingxia commented Jul 11, 2024

Uh oh!

xenolinux commented Jul 11, 2024

Uh oh!

jianping-shu commented Jul 15, 2024 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

xenolinux commented Aug 16, 2024

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!

openshift-ci Bot commented Aug 26, 2024

Uh oh!

xenolinux commented Aug 26, 2024

Uh oh!

kcarmichael08 commented Aug 26, 2024

Uh oh!

kcarmichael08 commented Aug 26, 2024

Uh oh!

kcarmichael08 commented Aug 26, 2024

Uh oh!

openshift-cherrypick-robot commented Aug 26, 2024

Uh oh!

xenolinux commented Jun 18, 2024 •

edited

Loading

ocpdocs-previewbot commented Jun 18, 2024 •

edited

Loading

huangmingxia Jul 5, 2024 •

edited

Loading

xenolinux commented Jul 11, 2024 •

edited

Loading

jianping-shu commented Jul 15, 2024 •

edited by openshift-ci Bot

Loading