apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "60020"
    uid: bbd1138e-a71a-49b4-9f0a-47cfe0be43ba
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:07:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.152538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 1.248829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 1.318852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 1.275044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 1.469837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:31:57Z"
    - latency: 1.286153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:30:57Z"
    - latency: 894.366µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:29:57Z"
    - latency: 977.734µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:28:57Z"
    - latency: 965.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:27:57Z"
    - latency: 1.188514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:26:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "61115"
    uid: 447a22c1-a921-45e4-b562-7d3992eda067
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:06:57Z"
      message: 'load-balancer-api-external: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.746612ms
      message: 'load-balancer-api-external: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:36:57Z"
    - latency: 9.494919ms
      message: 'load-balancer-api-external: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:36:57Z"
    - latency: 5.22876ms
      message: 'load-balancer-api-external: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 7.311301ms
      message: 'load-balancer-api-external: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 3.583127ms
      message: 'load-balancer-api-external: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 7.693241ms
      message: 'load-balancer-api-external: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 3.585614ms
      message: 'load-balancer-api-external: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 6.824207ms
      message: 'load-balancer-api-external: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 4.952498ms
      message: 'load-balancer-api-external: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 6.840573ms
      message: 'load-balancer-api-external: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "61114"
    uid: 5e97b7cd-0182-4114-b2e5-767fdf1c6556
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:06:57Z"
      message: 'load-balancer-api-internal: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.66805ms
      message: 'load-balancer-api-internal: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:36:57Z"
    - latency: 9.4529ms
      message: 'load-balancer-api-internal: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:36:57Z"
    - latency: 5.411004ms
      message: 'load-balancer-api-internal: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 7.265642ms
      message: 'load-balancer-api-internal: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 3.589022ms
      message: 'load-balancer-api-internal: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 7.607553ms
      message: 'load-balancer-api-internal: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 3.656766ms
      message: 'load-balancer-api-internal: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 6.848052ms
      message: 'load-balancer-api-internal: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 4.974005ms
      message: 'load-balancer-api-internal: tcp connection to a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 6.8502ms
      message: 'load-balancer-api-internal: resolved host name a9f97cf29a00f46edbfac24e4aae6517-df20e7d061263607.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-network-check-target-ip-10-0-135-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "60019"
    uid: ed35c504-3e24-42b5-895c-675e3f75c221
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:07:57Z"
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.178111ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 2.03576ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 1.981297ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 2.171758ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 2.147826ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:31:57Z"
    - latency: 2.09321ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:30:57Z"
    - latency: 2.113486ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:29:57Z"
    - latency: 2.189906ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:28:57Z"
    - latency: 1.965118ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:27:57Z"
    - latency: 2.214149ms
      message: 'network-check-target-ip-10-0-135-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:26:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-network-check-target-ip-10-0-141-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "60018"
    uid: 478ade5e-7716-475c-a2ab-9095972c292e
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:07:57Z"
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.057198ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 1.515624ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 925.404µs
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 1.087147ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 1.19833ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:31:57Z"
    - latency: 1.619014ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:30:57Z"
    - latency: 882.212µs
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:29:57Z"
    - latency: 1.300742ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:28:57Z"
    - latency: 1.28817ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:27:57Z"
    - latency: 1.020465ms
      message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:26:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-network-check-target-ip-10-0-142-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "60017"
    uid: c03a58aa-1788-4d47-b9c3-4d5f85d152ba
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:07:57Z"
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.056438ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 2.284699ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 2.358549ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 2.632493ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 2.311743ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:31:57Z"
    - latency: 2.183733ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:30:57Z"
    - latency: 2.318195ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:29:57Z"
    - latency: 2.15178ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:28:57Z"
    - latency: 2.006506ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:27:57Z"
    - latency: 2.1936ms
      message: 'network-check-target-ip-10-0-142-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:26:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T04:00:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-71-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-71.ec2.internal
      uid: aa80c992-2221-4338-8c57-25e110ba6d0f
    resourceVersion: "61113"
    uid: 86d60b15-a5a5-4a53-aea4-aaeabd4e1015
  spec:
    sourcePod: network-check-source-685456655f-kkw2d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T04:06:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.485µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:36:57Z"
    - latency: 3.229928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:36:57Z"
    - latency: 1.121813ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 2.216944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:35:57Z"
    - latency: 1.004652ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 2.132635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:34:57Z"
    - latency: 1.030411ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 1.962596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:33:57Z"
    - latency: 1.026321ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T04:32:57Z"
    - latency: 1.794402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T04:32:57Z"
kind: List
metadata:
  resourceVersion: ""