apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "30135"
    uid: 436454fc-3f22-4ccd-b46f-11378c916e4d
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:06:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.554µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:13:11Z"
    - latency: 814.084µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:12:11Z"
    - latency: 1.244813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 893.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 1.236451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 1.225007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 983.85µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 1.130718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:06:11Z"
    - latency: 1.264373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:05:11Z"
    - latency: 1.126116ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "28856"
    uid: ae039698-d77b-4c70-a325-3d2c2667ad9f
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:05:11Z"
      message: 'load-balancer-api-external: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.334651ms
      message: 'load-balancer-api-external: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 7.000822ms
      message: 'load-balancer-api-external: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 4.590893ms
      message: 'load-balancer-api-external: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 7.175908ms
      message: 'load-balancer-api-external: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 5.373379ms
      message: 'load-balancer-api-external: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 6.129434ms
      message: 'load-balancer-api-external: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 5.044804ms
      message: 'load-balancer-api-external: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 6.106068ms
      message: 'load-balancer-api-external: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 4.592514ms
      message: 'load-balancer-api-external: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 7.382321ms
      message: 'load-balancer-api-external: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:07:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "28857"
    uid: e6a66b9a-4f65-4aa4-86f3-b0a17f3c9d0b
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:05:11Z"
      message: 'load-balancer-api-internal: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.352987ms
      message: 'load-balancer-api-internal: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 6.92135ms
      message: 'load-balancer-api-internal: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 4.308929ms
      message: 'load-balancer-api-internal: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 7.305695ms
      message: 'load-balancer-api-internal: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 5.822776ms
      message: 'load-balancer-api-internal: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 6.056255ms
      message: 'load-balancer-api-internal: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 4.833556ms
      message: 'load-balancer-api-internal: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 6.164647ms
      message: 'load-balancer-api-internal: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 4.63012ms
      message: 'load-balancer-api-internal: tcp connection to a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 7.235458ms
      message: 'load-balancer-api-internal: resolved host name a9c75986f6f4c4fd9bc2e164c5cbe167-9f4c01ec4e7fe1e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:07:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-network-check-target-ip-10-0-128-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "30132"
    uid: 5d4425e4-b83b-4dd8-b552-7900588868dc
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:06:11Z"
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037118ms
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:13:11Z"
    - latency: 1.128952ms
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:12:11Z"
    - latency: 1.319367ms
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 1.246585ms
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 841.877µs
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 1.450315ms
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 966.887µs
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 1.095045ms
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:06:11Z"
    - latency: 805.505µs
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:05:11Z"
    - latency: 953.456µs
      message: 'network-check-target-ip-10-0-128-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-network-check-target-ip-10-0-138-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "30133"
    uid: f7c57b1e-17d7-46d9-81ff-9cc947a5f3c8
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:06:11Z"
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.899491ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:13:11Z"
    - latency: 2.16483ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:12:11Z"
    - latency: 2.09466ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 2.345792ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 1.875174ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 2.547712ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 2.382476ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 2.27674ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:06:11Z"
    - latency: 2.162362ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:05:11Z"
    - latency: 2.191127ms
      message: 'network-check-target-ip-10-0-138-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-network-check-target-ip-10-0-142-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "30134"
    uid: ed6ded88-54fe-4ab7-80f9-1ec7cff52ed4
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:06:11Z"
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.935016ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:13:11Z"
    - latency: 1.769008ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:12:11Z"
    - latency: 1.827903ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 1.839003ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 1.862013ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 1.849488ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 1.955415ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 1.984991ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:06:11Z"
    - latency: 2.592444ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:05:11Z"
    - latency: 1.959517ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T22:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-179-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-179.ec2.internal
      uid: 9e63fa55-bb81-471e-9449-65775281c790
    resourceVersion: "28854"
    uid: 042afa4b-3f3a-465f-a2d5-e2ca86d8f3eb
  spec:
    sourcePod: network-check-source-6947749cfc-xztxx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:05:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.135732ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 2.165557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:11:11Z"
    - latency: 1.052522ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 2.00264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:10:11Z"
    - latency: 836.567µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 1.829248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:09:11Z"
    - latency: 1.130959ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 1.571347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:08:11Z"
    - latency: 818.819µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:07:11Z"
    - latency: 2.441152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T23:07:11Z"
kind: List
metadata:
  resourceVersion: ""