apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "14404"
    uid: 2030abce-ad16-49a8-8dda-db1d6a3cf0b1
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.29µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 1.063734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 909.172µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.703069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.049186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 957.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 927.36µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "13965"
    uid: 43d6af5e-e272-4ffb-9ca6-f993b058477a
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:52:42Z"
      message: 'load-balancer-api-external: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.409301ms
      message: 'load-balancer-api-external: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 8.701337ms
      message: 'load-balancer-api-external: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 5.255894ms
      message: 'load-balancer-api-external: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 7.950291ms
      message: 'load-balancer-api-external: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 4.589434ms
      message: 'load-balancer-api-external: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 8.243917ms
      message: 'load-balancer-api-external: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 3.920089ms
      message: 'load-balancer-api-external: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 9.736102ms
      message: 'load-balancer-api-external: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 4.850652ms
      message: 'load-balancer-api-external: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 8.071947ms
      message: 'load-balancer-api-external: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:48:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "13964"
    uid: 4bab5c91-aad4-4360-9c86-039a7743d1ca
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:52:42Z"
      message: 'load-balancer-api-internal: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.562249ms
      message: 'load-balancer-api-internal: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 8.658543ms
      message: 'load-balancer-api-internal: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 5.278768ms
      message: 'load-balancer-api-internal: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 8.004953ms
      message: 'load-balancer-api-internal: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 4.609617ms
      message: 'load-balancer-api-internal: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 8.186563ms
      message: 'load-balancer-api-internal: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 3.900963ms
      message: 'load-balancer-api-internal: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 9.785273ms
      message: 'load-balancer-api-internal: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 4.856066ms
      message: 'load-balancer-api-internal: tcp connection to a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 8.139927ms
      message: 'load-balancer-api-internal: resolved host name a6339f1441d9a44b98803599a887b5c1-5bb736d6a0ec6baa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:48:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-139-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "14401"
    uid: 29843da0-4330-4e77-aedc-2bdd0ef34e38
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.501819ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 1.798989ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 1.944475ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.829419ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.79464ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 1.83641ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 1.899364ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-140-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "14403"
    uid: 7e07e6ab-c091-4af3-98f2-a4abc2553b3b
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.925989ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 1.884188ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 2.023934ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 2.852313ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 4.084446ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 2.533996ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 2.251597ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-141-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "14402"
    uid: ebd10aae-29cc-47e6-99b7-a99e4957efbd
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:53:42Z"
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 753.057µs
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:53:42Z"
    - latency: 821.447µs
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 1.229229ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.193756ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 842.876µs
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 922.968µs
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 1.1752ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-177-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-177.ec2.internal
      uid: 694db281-25a1-48b9-9f79-7ff8507b0d71
    resourceVersion: "13963"
    uid: 67d2d5bc-5e74-4f5a-a757-1b4bd7287e9d
  spec:
    sourcePod: network-check-source-685456655f-49cnz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:52:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 2.237979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:52:42Z"
    - latency: 809.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 1.776147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:51:42Z"
    - latency: 749.289µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 1.61617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:50:42Z"
    - latency: 810.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 1.703178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:49:42Z"
    - latency: 912.363µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:48:42Z"
    - latency: 1.749523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:48:42Z"
kind: List
metadata:
  resourceVersion: ""