apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "53781"
    uid: 62937cae-fff2-4c11-9621-db5b7ccc1f92
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:26:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.917µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 1.781274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 1.218066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 913.764µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:09Z"
    - latency: 1.139752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:09Z"
    - latency: 1.068509ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:09Z"
    - latency: 1.202856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:09Z"
    - latency: 1.140722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:09Z"
    - latency: 1.146485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:09Z"
    - latency: 1.273367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "55438"
    uid: 8458d06e-6130-4f6c-ba5a-a793b3216628
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:25:09Z"
      message: 'load-balancer-api-external: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.074743ms
      message: 'load-balancer-api-external: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:09Z"
    - latency: 8.953558ms
      message: 'load-balancer-api-external: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:49:09Z"
    - latency: 5.523876ms
      message: 'load-balancer-api-external: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:09Z"
    - latency: 9.227787ms
      message: 'load-balancer-api-external: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:48:09Z"
    - latency: 3.89392ms
      message: 'load-balancer-api-external: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 7.957591ms
      message: 'load-balancer-api-external: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 5.305757ms
      message: 'load-balancer-api-external: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 11.871953ms
      message: 'load-balancer-api-external: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 3.583121ms
      message: 'load-balancer-api-external: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 6.863626ms
      message: 'load-balancer-api-external: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:45:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "55439"
    uid: ad17655c-bc64-4969-9279-868e137cc00b
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:25:09Z"
      message: 'load-balancer-api-internal: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.221662ms
      message: 'load-balancer-api-internal: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:09Z"
    - latency: 8.917577ms
      message: 'load-balancer-api-internal: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:49:09Z"
    - latency: 5.449461ms
      message: 'load-balancer-api-internal: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:09Z"
    - latency: 9.270703ms
      message: 'load-balancer-api-internal: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:48:09Z"
    - latency: 4.010008ms
      message: 'load-balancer-api-internal: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 7.925516ms
      message: 'load-balancer-api-internal: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 5.29255ms
      message: 'load-balancer-api-internal: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 11.913496ms
      message: 'load-balancer-api-internal: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 6.806318ms
      message: 'load-balancer-api-internal: tcp connection to adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 6.904466ms
      message: 'load-balancer-api-internal: resolved host name adc9ea4b2b8584b7e98e1a2ec81c2e28-b38965c1835a65e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:45:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-network-check-target-ip-10-0-129-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "53780"
    uid: f8d95f58-3834-4cdd-8ac1-6962b2287031
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:26:09Z"
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 759.214µs
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 971.567µs
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 1.124908ms
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 999.704µs
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:09Z"
    - latency: 1.151151ms
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:09Z"
    - latency: 829.406µs
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:09Z"
    - latency: 952.767µs
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:09Z"
    - latency: 1.156412ms
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:09Z"
    - latency: 1.031657ms
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:09Z"
    - latency: 995.874µs
      message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-network-check-target-ip-10-0-138-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "53779"
    uid: 649de0c2-6a31-4d79-a55d-ffa12d688e3d
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:26:09Z"
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.086888ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 2.520422ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 2.690616ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 2.531114ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:09Z"
    - latency: 2.348758ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:09Z"
    - latency: 2.799174ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:09Z"
    - latency: 3.216977ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:09Z"
    - latency: 1.910716ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:09Z"
    - latency: 2.312966ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:09Z"
    - latency: 2.622571ms
      message: 'network-check-target-ip-10-0-138-71: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-network-check-target-ip-10-0-142-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "53778"
    uid: cd16d985-da62-428f-ae01-6959ee687249
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:26:09Z"
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263377ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 2.449967ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 2.480837ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 2.479269ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:09Z"
    - latency: 2.531198ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:09Z"
    - latency: 2.444511ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:09Z"
    - latency: 2.423936ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:09Z"
    - latency: 2.479726ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:09Z"
    - latency: 2.300025ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:09Z"
    - latency: 2.590293ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:19:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-114-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-114.ec2.internal
      uid: ffa5a9f4-c2b8-439f-920f-2bdef32d8d83
    resourceVersion: "55436"
    uid: 8d16e231-bfcc-422c-a61b-7798ed8d0883
  spec:
    sourcePod: network-check-source-685456655f-n4jkz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:25:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.786µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:09Z"
    - latency: 2.119217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:49:09Z"
    - latency: 743.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:09Z"
    - latency: 1.884509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:48:09Z"
    - latency: 954.666µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 1.729705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:47:09Z"
    - latency: 953.453µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 1.828569ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:46:09Z"
    - latency: 982.496µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:09Z"
    - latency: 1.813018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:45:09Z"
kind: List
metadata:
  resourceVersion: ""