apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "19422"
    uid: 7d53ccfe-1dfb-4e1f-940c-7e4771f0f445
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:33:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 930.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 973.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 1.073663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:07Z"
    - latency: 1.500364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:07Z"
    - latency: 824.031µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:07Z"
    - latency: 841.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:07Z"
    - latency: 1.196265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:07Z"
    - latency: 1.511533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:07Z"
    - latency: 1.113067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:07Z"
    - latency: 954.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "20739"
    uid: d70938d5-55c1-4047-8608-7501179a1360
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:32:07Z"
      message: 'load-balancer-api-external: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.675154ms
      message: 'load-balancer-api-external: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:50:07Z"
    - latency: 8.126298ms
      message: 'load-balancer-api-external: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:50:07Z"
    - latency: 4.576618ms
      message: 'load-balancer-api-external: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:49:07Z"
    - latency: 8.606396ms
      message: 'load-balancer-api-external: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:49:07Z"
    - latency: 3.932943ms
      message: 'load-balancer-api-external: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:48:07Z"
    - latency: 8.672878ms
      message: 'load-balancer-api-external: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:48:07Z"
    - latency: 4.871017ms
      message: 'load-balancer-api-external: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 8.592638ms
      message: 'load-balancer-api-external: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 5.238441ms
      message: 'load-balancer-api-external: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 12.541635ms
      message: 'load-balancer-api-external: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:46:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "20740"
    uid: 32577ab2-da59-4535-b2c2-63c58cd6799d
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:32:07Z"
      message: 'load-balancer-api-internal: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.695942ms
      message: 'load-balancer-api-internal: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:50:07Z"
    - latency: 8.109694ms
      message: 'load-balancer-api-internal: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:50:07Z"
    - latency: 3.374393ms
      message: 'load-balancer-api-internal: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:49:07Z"
    - latency: 8.542458ms
      message: 'load-balancer-api-internal: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:49:07Z"
    - latency: 5.396357ms
      message: 'load-balancer-api-internal: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:48:07Z"
    - latency: 8.700119ms
      message: 'load-balancer-api-internal: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:48:07Z"
    - latency: 4.840886ms
      message: 'load-balancer-api-internal: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 8.634232ms
      message: 'load-balancer-api-internal: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 5.232143ms
      message: 'load-balancer-api-internal: tcp connection to a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 12.607645ms
      message: 'load-balancer-api-internal: resolved host name a81cd40fc9ce340e89727f11a9303b22-028774fe42895f28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:46:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-network-check-target-ip-10-0-131-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "19419"
    uid: 04789e84-e1f8-4003-a70f-eb0232803d3c
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:33:07Z"
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.914µs
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 1.272445ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 817.391µs
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:07Z"
    - latency: 839.455µs
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:07Z"
    - latency: 1.523289ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:07Z"
    - latency: 894.65µs
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:07Z"
    - latency: 1.105505ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:07Z"
    - latency: 968.017µs
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:07Z"
    - latency: 1.066979ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:07Z"
    - latency: 1.209715ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-network-check-target-ip-10-0-137-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "19420"
    uid: 1a208448-c086-4c4a-a5a9-1e87e611d78b
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:33:07Z"
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.592777ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 2.722601ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 2.028667ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:07Z"
    - latency: 2.320629ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:07Z"
    - latency: 2.244574ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:07Z"
    - latency: 2.234942ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:07Z"
    - latency: 2.275042ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:07Z"
    - latency: 2.583109ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:07Z"
    - latency: 2.012243ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:07Z"
    - latency: 2.545957ms
      message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-network-check-target-ip-10-0-138-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "19421"
    uid: b8ea0865-159f-4abe-a5b5-64d12c933842
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:33:07Z"
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345006ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 2.113076ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 1.829816ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:07Z"
    - latency: 2.21163ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:07Z"
    - latency: 2.518633ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:07Z"
    - latency: 1.991361ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:07Z"
    - latency: 2.000852ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:07Z"
    - latency: 2.222772ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:07Z"
    - latency: 2.03838ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:07Z"
    - latency: 1.960786ms
      message: 'network-check-target-ip-10-0-138-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:26:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-138-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-138.ec2.internal
      uid: ab024802-05e1-4157-b5e5-d44c89e5d407
    resourceVersion: "20738"
    uid: 4f9807bd-f4c2-405f-89b0-dbda5147cb90
  spec:
    sourcePod: network-check-source-7d88cb55d8-dr9xk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:32:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001877ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:50:07Z"
    - latency: 1.671552ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:50:07Z"
    - latency: 914.104µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:49:07Z"
    - latency: 1.604861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:49:07Z"
    - latency: 1.224539ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:48:07Z"
    - latency: 1.906664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:48:07Z"
    - latency: 1.015939ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 1.70003ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:47:07Z"
    - latency: 874.733µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:07Z"
    - latency: 2.024018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:46:07Z"
kind: List
metadata:
  resourceVersion: ""