apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39827"
    uid: 34c2ca76-543d-46a6-99f0-ac6a5d557951
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:11:45Z"
    - latency: 1.19425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 1.100033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 1.602808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 1.065497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 1.179355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 891.558µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:05:45Z"
    - latency: 1.180945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:45Z"
    - latency: 1.207443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:45Z"
    - latency: 979.94µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39339"
    uid: 7d01465e-f00c-4ee9-a569-4e7eb724a0e4
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:45Z"
      message: 'load-balancer-api-external: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.441355ms
      message: 'load-balancer-api-external: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 7.550215ms
      message: 'load-balancer-api-external: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 4.423942ms
      message: 'load-balancer-api-external: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 8.579521ms
      message: 'load-balancer-api-external: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 5.392603ms
      message: 'load-balancer-api-external: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 6.728288ms
      message: 'load-balancer-api-external: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 4.840555ms
      message: 'load-balancer-api-external: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 11.648178ms
      message: 'load-balancer-api-external: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 6.639661ms
      message: 'load-balancer-api-external: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 6.773898ms
      message: 'load-balancer-api-external: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:06:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39340"
    uid: 8cef4ef6-5c02-4ced-a4c9-f52b1dc19509
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:45Z"
      message: 'load-balancer-api-internal: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.837703ms
      message: 'load-balancer-api-internal: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 7.526095ms
      message: 'load-balancer-api-internal: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 4.828293ms
      message: 'load-balancer-api-internal: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 8.627931ms
      message: 'load-balancer-api-internal: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 5.38691ms
      message: 'load-balancer-api-internal: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 6.699004ms
      message: 'load-balancer-api-internal: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 4.782811ms
      message: 'load-balancer-api-internal: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 11.594941ms
      message: 'load-balancer-api-internal: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 6.396047ms
      message: 'load-balancer-api-internal: tcp connection to af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 6.739357ms
      message: 'load-balancer-api-internal: resolved host name af38b9932af4d40f0a2222f01093b004-8db3969f11f6aa88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:06:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-network-check-target-ip-10-0-129-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39826"
    uid: 5a39929e-00ff-47e9-8e1d-b816f3bca0a3
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:45Z"
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.057441ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:11:45Z"
    - latency: 2.04853ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 2.244329ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 2.508811ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 2.261911ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 2.169523ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 2.142456ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:05:45Z"
    - latency: 2.302997ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:45Z"
    - latency: 1.981548ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:45Z"
    - latency: 2.228883ms
      message: 'network-check-target-ip-10-0-129-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-network-check-target-ip-10-0-135-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39825"
    uid: febfb384-d814-4cab-b2af-c224a87f4175
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:45Z"
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.443434ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:11:45Z"
    - latency: 1.150717ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 1.304191ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 959.848µs
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 1.625407ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 938.131µs
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 1.573551ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:05:45Z"
    - latency: 917.006µs
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:45Z"
    - latency: 1.534116ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:45Z"
    - latency: 1.421721ms
      message: 'network-check-target-ip-10-0-135-239: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-network-check-target-ip-10-0-140-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39824"
    uid: 09acee5a-bb08-44fa-8ed6-1dc0d164f864
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:45Z"
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.146893ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:11:45Z"
    - latency: 2.027288ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 2.022041ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 2.166818ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 1.81672ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 1.874265ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 1.979057ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:05:45Z"
    - latency: 2.036239ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:45Z"
    - latency: 1.885231ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:45Z"
    - latency: 1.937486ms
      message: 'network-check-target-ip-10-0-140-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-239.ec2.internal
      uid: 46e4a351-fcd4-4c0c-a5ba-499aeb70c4ef
    resourceVersion: "39338"
    uid: 811190cc-cfbd-42f1-b5b3-1b28255523a7
  spec:
    sourcePod: network-check-source-685456655f-cbsx2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.491µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 1.66802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:10:45Z"
    - latency: 1.158852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 2.27819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:09:45Z"
    - latency: 1.351292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 1.763125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:08:45Z"
    - latency: 968.099µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 2.337667ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:07:45Z"
    - latency: 972.418µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:06:45Z"
    - latency: 1.79288ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:06:45Z"
kind: List
metadata:
  resourceVersion: ""