OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates by dfitzmau · Pull Request #80110 · openshift/openshift-docs

dfitzmau · 2024-08-07T10:47:49Z

Updates the doc to include Adding a NodePortService ingresscontroller from this SME document.

Version(s):
4.12+

Issue:
(https://issues.redhat.com/browse/OSDOCS-8653)

Link to docs preview:

Configuring ingress cluster traffic using an Ingress Controller: removed Cnfiguring the Ingress Controller endpoint publishing strategy section from this doc
Configuring the Ingress Controller endpoint publishing strategy-single NodePort service to an Ingress Controller

Preview for link updates:

SME has approved this change.
QE has approved this change.

Additional information:

SME doc

openshift-ci-robot · 2024-08-07T10:47:51Z

@dfitzmau: No Jira issue with key deepdive-3 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Version(s):

Issue:

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 openshift-eng/jira-lifecycle-plugin repository.

ocpdocs-previewbot · 2024-08-07T10:55:34Z

🤖 Fri Sep 13 13:09:44 - Prow CI generated the docs preview:

openshift-ci-robot · 2024-08-07T14:41:01Z

@dfitzmau: No Jira issue with key deepdive-3 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Version(s):
4.12+

Issue:
(https://issues.redhat.com/browse/OSDOCS-9350)

Link to docs preview:

SME has approved this change.

QE has approved this change.

Additional information:

SME doc

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.

lihongan · 2024-09-05T09:49:20Z

+
+[source,terminal]
+----
+$ oc curl hello-openshift.nodeportsvc.ipi-cluster.example.com:<port> 


It is curl http://hello-openshift.nodeportsvc.ipi-cluster.example.com:<port> not oc curl ...

should provide description of <port>

Port is the nodeport we get from the nodeport service, `80:32432/TCP` means we should use `32432` here.

See Line 83 and 88, 80:32432/TCP,443:31366/TCP means for http route we should use nodeport 32432, for https should use nodeport 31366

lpettyjo

Otherwise, LGTM!

lihongan · 2024-09-13T09:31:36Z

LGTM. thank you @dfitzmau

openshift-ci-robot · 2024-09-13T10:05:40Z

@dfitzmau: No Jira issue with key deepdive-3 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Updates the doc to include Adding a NodePortService ingresscontroller from this SME document.

Version(s):
4.12+

Issue:
(https://issues.redhat.com/browse/OSDOCS-8653)

Link to docs preview:

Configuring ingress cluster traffic using an Ingress Controller: removed Cnfiguring the Ingress Controller endpoint publishing strategy section from this doc

Configuring the Ingress Controller endpoint publishing strategy-single NodePort service to an Ingress Controller

Preview for link updates:

AWS Restricting the API server to private: Updated a link

Azure Restricting the API server to private: Updated a link

Managed DNS management policy: Updated a link

Restricting the API server to private: Updated a link

SME has approved this change.

QE has approved this change.

Additional information:

SME doc

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 · 2024-09-13T13:11:23Z

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

dfitzmau · 2024-09-13T14:49:29Z

/cherrypick enterprise-4.17

dfitzmau · 2024-09-13T14:49:33Z

/cherrypick enterprise-4.16

dfitzmau · 2024-09-13T14:49:37Z

/cherrypick enterprise-4.15

dfitzmau · 2024-09-13T14:49:42Z

/cherrypick enterprise-4.14

dfitzmau · 2024-09-13T14:49:47Z

/cherrypick enterprise-4.13

dfitzmau · 2024-09-13T14:49:50Z

/cherrypick enterprise-4.12

openshift-cherrypick-robot · 2024-09-13T14:50:21Z

@dfitzmau: new pull request created: #81802

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-cherrypick-robot · 2024-09-13T14:50:22Z

@dfitzmau: #80110 failed to apply on top of branch "enterprise-4.16":

Applying: OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates
.git/rebase-apply/patch:206: trailing whitespace.
Instead of creating a `NodePort`-type `Service` for each project, you can create a custom Ingress Controller to use the `NodePortService` endpoint publishing strategy. To prevent port conflicts, consider this configuration for your Ingress Controller when you want to apply a set of routes, through Ingress sharding, to nodes that might already have a `HostNetwork` Ingress Controller.  
.git/rebase-apply/patch:212: trailing whitespace.
* You must append the port that is assigned to the `NodePort`-type `Service` in the route so that you can access application pods. 
.git/rebase-apply/patch:246: trailing whitespace.
      type: NodePortService 
.git/rebase-apply/patch:316: trailing whitespace.
You must specify the domain name of your custom Ingress Controller in the `--hostname` argument. If you do not do this, the Ingress Operator uses the default Ingress Controller to serve all the routes for your cluster. 
.git/rebase-apply/patch:436: trailing whitespace.
// Creating a project and service  
warning: 5 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
A	modules/hcp-virt-wildcard-dns.adoc
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): modules/hcp-virt-wildcard-dns.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of modules/hcp-virt-wildcard-dns.adoc left in tree.
Auto-merging machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
Auto-merging _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-9350-deepdive-3: endpointPublishingStrategy updates
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.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-09-13T14:50:26Z

@dfitzmau: #80110 failed to apply on top of branch "enterprise-4.15":

Applying: OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates
.git/rebase-apply/patch:206: trailing whitespace.
Instead of creating a `NodePort`-type `Service` for each project, you can create a custom Ingress Controller to use the `NodePortService` endpoint publishing strategy. To prevent port conflicts, consider this configuration for your Ingress Controller when you want to apply a set of routes, through Ingress sharding, to nodes that might already have a `HostNetwork` Ingress Controller.  
.git/rebase-apply/patch:212: trailing whitespace.
* You must append the port that is assigned to the `NodePort`-type `Service` in the route so that you can access application pods. 
.git/rebase-apply/patch:246: trailing whitespace.
      type: NodePortService 
.git/rebase-apply/patch:316: trailing whitespace.
You must specify the domain name of your custom Ingress Controller in the `--hostname` argument. If you do not do this, the Ingress Operator uses the default Ingress Controller to serve all the routes for your cluster. 
.git/rebase-apply/patch:436: trailing whitespace.
// Creating a project and service  
warning: 5 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
A	modules/hcp-virt-wildcard-dns.adoc
M	networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
CONFLICT (modify/delete): modules/hcp-virt-wildcard-dns.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of modules/hcp-virt-wildcard-dns.adoc left in tree.
Auto-merging machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
Auto-merging _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-9350-deepdive-3: endpointPublishingStrategy updates
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.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-09-13T14:50:30Z

@dfitzmau: #80110 failed to apply on top of branch "enterprise-4.14":

Applying: OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates
.git/rebase-apply/patch:206: trailing whitespace.
Instead of creating a `NodePort`-type `Service` for each project, you can create a custom Ingress Controller to use the `NodePortService` endpoint publishing strategy. To prevent port conflicts, consider this configuration for your Ingress Controller when you want to apply a set of routes, through Ingress sharding, to nodes that might already have a `HostNetwork` Ingress Controller.  
.git/rebase-apply/patch:212: trailing whitespace.
* You must append the port that is assigned to the `NodePort`-type `Service` in the route so that you can access application pods. 
.git/rebase-apply/patch:246: trailing whitespace.
      type: NodePortService 
.git/rebase-apply/patch:316: trailing whitespace.
You must specify the domain name of your custom Ingress Controller in the `--hostname` argument. If you do not do this, the Ingress Operator uses the default Ingress Controller to serve all the routes for your cluster. 
.git/rebase-apply/patch:436: trailing whitespace.
// Creating a project and service  
warning: 5 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
A	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc
A	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
A	modules/hcp-virt-wildcard-dns.adoc
M	networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
M	post_installation_configuration/configuring-private-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging post_installation_configuration/configuring-private-cluster.adoc
Auto-merging networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
CONFLICT (modify/delete): modules/hcp-virt-wildcard-dns.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of modules/hcp-virt-wildcard-dns.adoc left in tree.
CONFLICT (modify/delete): machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc left in tree.
CONFLICT (modify/delete): machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc left in tree.
Auto-merging _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-9350-deepdive-3: endpointPublishingStrategy updates
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.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-sigs/prow repository.

openshift-cherrypick-robot · 2024-09-13T14:50:35Z

@dfitzmau: #80110 failed to apply on top of branch "enterprise-4.13":

Applying: OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates
.git/rebase-apply/patch:206: trailing whitespace.
Instead of creating a `NodePort`-type `Service` for each project, you can create a custom Ingress Controller to use the `NodePortService` endpoint publishing strategy. To prevent port conflicts, consider this configuration for your Ingress Controller when you want to apply a set of routes, through Ingress sharding, to nodes that might already have a `HostNetwork` Ingress Controller.  
.git/rebase-apply/patch:212: trailing whitespace.
* You must append the port that is assigned to the `NodePort`-type `Service` in the route so that you can access application pods. 
.git/rebase-apply/patch:246: trailing whitespace.
      type: NodePortService 
.git/rebase-apply/patch:316: trailing whitespace.
You must specify the domain name of your custom Ingress Controller in the `--hostname` argument. If you do not do this, the Ingress Operator uses the default Ingress Controller to serve all the routes for your cluster. 
.git/rebase-apply/patch:436: trailing whitespace.
// Creating a project and service  
warning: 5 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
A	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc
A	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
A	modules/hcp-virt-wildcard-dns.adoc
M	networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
M	post_installation_configuration/configuring-private-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging post_installation_configuration/configuring-private-cluster.adoc
CONFLICT (content): Merge conflict in post_installation_configuration/configuring-private-cluster.adoc
Auto-merging networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
CONFLICT (modify/delete): modules/hcp-virt-wildcard-dns.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of modules/hcp-virt-wildcard-dns.adoc left in tree.
CONFLICT (modify/delete): machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc left in tree.
CONFLICT (modify/delete): machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc left in tree.
Auto-merging _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-9350-deepdive-3: endpointPublishingStrategy updates
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-sigs/prow repository.

openshift-cherrypick-robot · 2024-09-13T14:50:38Z

@dfitzmau: #80110 failed to apply on top of branch "enterprise-4.12":

Applying: OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates
.git/rebase-apply/patch:206: trailing whitespace.
Instead of creating a `NodePort`-type `Service` for each project, you can create a custom Ingress Controller to use the `NodePortService` endpoint publishing strategy. To prevent port conflicts, consider this configuration for your Ingress Controller when you want to apply a set of routes, through Ingress sharding, to nodes that might already have a `HostNetwork` Ingress Controller.  
.git/rebase-apply/patch:212: trailing whitespace.
* You must append the port that is assigned to the `NodePort`-type `Service` in the route so that you can access application pods. 
.git/rebase-apply/patch:246: trailing whitespace.
      type: NodePortService 
.git/rebase-apply/patch:316: trailing whitespace.
You must specify the domain name of your custom Ingress Controller in the `--hostname` argument. If you do not do this, the Ingress Operator uses the default Ingress Controller to serve all the routes for your cluster. 
.git/rebase-apply/patch:436: trailing whitespace.
// Creating a project and service  
warning: 5 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
A	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc
A	machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc
A	modules/hcp-virt-wildcard-dns.adoc
M	networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
M	post_installation_configuration/configuring-private-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging post_installation_configuration/configuring-private-cluster.adoc
CONFLICT (content): Merge conflict in post_installation_configuration/configuring-private-cluster.adoc
Auto-merging networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
CONFLICT (modify/delete): modules/hcp-virt-wildcard-dns.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of modules/hcp-virt-wildcard-dns.adoc left in tree.
CONFLICT (modify/delete): machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc left in tree.
CONFLICT (modify/delete): machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc deleted in HEAD and modified in OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates. Version OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates of machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc left in tree.
Auto-merging _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-9350-deepdive-3: endpointPublishingStrategy updates
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-sigs/prow repository.

openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 7, 2024

dfitzmau force-pushed the OSDOCS-9350-deepdive-3 branch from ed158ab to 9e48fc9 Compare August 7, 2024 10:48

dfitzmau force-pushed the OSDOCS-9350-deepdive-3 branch 5 times, most recently from a78482b to 9ef6c2b Compare August 7, 2024 12:00

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

dfitzmau force-pushed the OSDOCS-9350-deepdive-3 branch 4 times, most recently from a47e37a to cded28f Compare August 7, 2024 14:34

dfitzmau force-pushed the OSDOCS-9350-deepdive-3 branch 14 times, most recently from 9915cc5 to 5de0305 Compare August 8, 2024 14:34

lihongan reviewed Sep 5, 2024

View reviewed changes

dfitzmau force-pushed the OSDOCS-9350-deepdive-3 branch 3 times, most recently from 3c92c84 to e789087 Compare September 5, 2024 10:50

lpettyjo 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 Sep 5, 2024

lpettyjo reviewed Sep 5, 2024

View reviewed changes

lihongan reviewed Sep 13, 2024

View reviewed changes

Comment thread modules/nw-ingress-controller-nodeportservice-projects.adoc Outdated

OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates

c9d8a85

openshift-cherrypick-robot mentioned this pull request Sep 13, 2024

[enterprise-4.17] OSDOCS-9350-deepdive-3: endpointPublishingStrategy updates #81802

Merged

Conversation

dfitzmau commented Aug 7, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 7, 2024

Uh oh!

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

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 7, 2024

Uh oh!

lihongan Sep 5, 2024

Choose a reason for hiding this comment

Uh oh!

dfitzmau Sep 5, 2024

Choose a reason for hiding this comment

Uh oh!

lpettyjo left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

lihongan commented Sep 13, 2024

Uh oh!

openshift-ci-robot commented Sep 13, 2024

Uh oh!

openshift-ci Bot commented Sep 13, 2024

Uh oh!

dfitzmau commented Sep 13, 2024

Uh oh!

dfitzmau commented Sep 13, 2024

Uh oh!

dfitzmau commented Sep 13, 2024

Uh oh!

dfitzmau commented Sep 13, 2024

Uh oh!

dfitzmau commented Sep 13, 2024

Uh oh!

dfitzmau commented Sep 13, 2024

Uh oh!

openshift-cherrypick-robot commented Sep 13, 2024

Uh oh!

openshift-cherrypick-robot commented Sep 13, 2024

Uh oh!

openshift-cherrypick-robot commented Sep 13, 2024

Uh oh!

openshift-cherrypick-robot commented Sep 13, 2024

Uh oh!

openshift-cherrypick-robot commented Sep 13, 2024

Uh oh!

openshift-cherrypick-robot commented Sep 13, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

dfitzmau commented Aug 7, 2024 •

edited

Loading

ocpdocs-previewbot commented Aug 7, 2024 •

edited

Loading