apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63432"
    uid: a7a7781a-de18-458e-937d-9c0c2a397192
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:59:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.849752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 795.841µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 1.066235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 864.23µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 1.533871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 1.142922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:29:56Z"
    - latency: 1.570476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:28:56Z"
    - latency: 946.363µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:27:56Z"
    - latency: 1.097276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:26:56Z"
    - latency: 1.356973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63435"
    uid: c5315ae2-2948-461d-b22c-91c433df7964
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:58:56Z"
      message: 'load-balancer-api-external: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.764392ms
      message: 'load-balancer-api-external: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 7.269982ms
      message: 'load-balancer-api-external: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 5.52153ms
      message: 'load-balancer-api-external: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 7.577988ms
      message: 'load-balancer-api-external: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 3.763876ms
      message: 'load-balancer-api-external: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 6.79179ms
      message: 'load-balancer-api-external: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 5.167063ms
      message: 'load-balancer-api-external: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 6.895102ms
      message: 'load-balancer-api-external: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 3.885742ms
      message: 'load-balancer-api-external: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 7.877916ms
      message: 'load-balancer-api-external: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:30:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63436"
    uid: a9bd9361-39af-4739-b4c8-c68fa2b2c50d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:58:56Z"
      message: 'load-balancer-api-internal: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.742097ms
      message: 'load-balancer-api-internal: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 7.340577ms
      message: 'load-balancer-api-internal: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 4.239589ms
      message: 'load-balancer-api-internal: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 7.586995ms
      message: 'load-balancer-api-internal: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 4.154211ms
      message: 'load-balancer-api-internal: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 6.884021ms
      message: 'load-balancer-api-internal: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 3.763058ms
      message: 'load-balancer-api-internal: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 7.083058ms
      message: 'load-balancer-api-internal: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 3.542981ms
      message: 'load-balancer-api-internal: tcp connection to ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 7.826467ms
      message: 'load-balancer-api-internal: resolved host name ab40c3c0071be460987699f28114f599-41d673c89868f7c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:30:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-network-check-target-ip-10-0-130-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63431"
    uid: a51f739d-e82a-4322-ae59-a201bea3364a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:59:56Z"
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249095ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 1.956617ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 2.321326ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 2.299713ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 2.372274ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 2.111079ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:29:56Z"
    - latency: 2.107661ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:28:56Z"
    - latency: 1.920773ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:27:56Z"
    - latency: 2.180236ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:26:56Z"
    - latency: 2.350949ms
      message: 'network-check-target-ip-10-0-130-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-network-check-target-ip-10-0-132-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63429"
    uid: f1660e1b-14b3-4156-b2b5-48bf6dda42c9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:59:56Z"
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.848176ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 1.742479ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 1.514277ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 1.900031ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 2.20204ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 1.977933ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:29:56Z"
    - latency: 2.07434ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:28:56Z"
    - latency: 1.919919ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:27:56Z"
    - latency: 2.092964ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:26:56Z"
    - latency: 2.091142ms
      message: 'network-check-target-ip-10-0-132-166: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-network-check-target-ip-10-0-143-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63428"
    uid: 36d61257-b12b-4b46-9ca7-5ba26467f263
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:59:56Z"
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.068µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 1.077746ms
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 829.4µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 1.133635ms
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 898.068µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 947.699µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:29:56Z"
    - latency: 971.466µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:28:56Z"
    - latency: 879.408µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:27:56Z"
    - latency: 939.327µs
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:26:56Z"
    - latency: 1.080866ms
      message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:25:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T11:52:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-104-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-104.ec2.internal
      uid: 020c239a-1a00-4ec0-bce1-0e7222996f8f
    resourceVersion: "63430"
    uid: 66222ba4-31d6-4fbb-a9a6-1e42b1d24a9b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7vrx2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T11:58:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.081229ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 1.85314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:34:56Z"
    - latency: 1.008197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 1.839023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:33:56Z"
    - latency: 1.092489ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 1.696361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:32:56Z"
    - latency: 904.302µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 1.696839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:31:56Z"
    - latency: 909.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T12:30:56Z"
    - latency: 2.114405ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T12:30:56Z"
kind: List
metadata:
  resourceVersion: ""