apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "24841"
    uid: 7f703d47-006b-4245-add2-aa932beb30dc
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:18:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.283253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:18:58Z"
    - latency: 1.037785ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 832.049µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 967.376µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 1.103219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 930.609µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 1.03394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "23701"
    uid: 423665de-51c2-4e2a-befa-eee8774f17c3
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:17:58Z"
      message: 'load-balancer-api-external: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.726989ms
      message: 'load-balancer-api-external: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 8.995081ms
      message: 'load-balancer-api-external: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 4.493715ms
      message: 'load-balancer-api-external: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 7.138748ms
      message: 'load-balancer-api-external: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 5.178408ms
      message: 'load-balancer-api-external: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 8.531862ms
      message: 'load-balancer-api-external: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 5.311805ms
      message: 'load-balancer-api-external: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 7.258898ms
      message: 'load-balancer-api-external: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 5.709414ms
      message: 'load-balancer-api-external: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 6.908173ms
      message: 'load-balancer-api-external: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:13:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "23700"
    uid: 6946ee1e-1e19-43e9-b52b-2e823fa4c8d6
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:17:58Z"
      message: 'load-balancer-api-internal: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.769183ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 8.927186ms
      message: 'load-balancer-api-internal: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 4.930196ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 7.185064ms
      message: 'load-balancer-api-internal: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 4.585838ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 8.510377ms
      message: 'load-balancer-api-internal: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 5.286543ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 7.372728ms
      message: 'load-balancer-api-internal: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 5.722768ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 6.871905ms
      message: 'load-balancer-api-internal: resolved host name a9ed9d523d3d7471f8118f2f7ad642f8-a9fb274a5b7f261e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:13:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-network-check-target-ip-10-0-128-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "24835"
    uid: c3b73123-13f7-476b-a5cc-1ae30f95d083
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:18:58Z"
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.852396ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:18:58Z"
    - latency: 1.249871ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 944.657µs
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 1.414889ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 1.988025ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 986.531µs
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 1.534872ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-network-check-target-ip-10-0-139-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "24837"
    uid: 240a1063-6424-4835-8a56-680ac21ef31e
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:18:58Z"
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.137843ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:18:58Z"
    - latency: 2.110888ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 2.033183ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 2.437974ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 1.961123ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 2.342708ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 2.583514ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-network-check-target-ip-10-0-142-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "24836"
    uid: 714db0d9-839e-44ef-9aa9-79265d81cbee
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:18:58Z"
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.648058ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:18:58Z"
    - latency: 2.448955ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 1.955881ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 2.306068ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 2.157102ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 1.976945ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 2.244755ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-37.ec2.internal
      uid: f5c43ad6-268c-4a3c-b0a7-571a92770a39
    resourceVersion: "23699"
    uid: 98a2f343-0ae4-4065-b0ff-5bf5a4467c89
  spec:
    sourcePod: network-check-source-dbd9cf844-c4qhr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:17:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.062µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 1.897825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:17:58Z"
    - latency: 996.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 2.172714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:16:58Z"
    - latency: 959.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 2.020561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:15:58Z"
    - latency: 887.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 2.043366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:14:58Z"
    - latency: 791.627µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:13:58Z"
    - latency: 1.683006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:13:58Z"
kind: List
metadata:
  resourceVersion: ""