apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "55148"
    uid: ad8abbe8-74bb-46bf-8966-107c1409b1bf
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:23:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 1.21912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 995.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 1.216271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:27Z"
    - latency: 916.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:27Z"
    - latency: 1.570422ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:27Z"
    - latency: 1.935851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:38:27Z"
    - latency: 1.224105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:37:27Z"
    - latency: 896.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:36:27Z"
    - latency: 1.007669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:35:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "56903"
    uid: d8a9a981-2ef8-4bba-b8d2-54f3ff65b553
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:22:27Z"
      message: 'load-balancer-api-external: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.360562ms
      message: 'load-balancer-api-external: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:27Z"
    - latency: 8.292443ms
      message: 'load-balancer-api-external: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:46:27Z"
    - latency: 5.044203ms
      message: 'load-balancer-api-external: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:27Z"
    - latency: 9.168195ms
      message: 'load-balancer-api-external: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:45:27Z"
    - latency: 4.661998ms
      message: 'load-balancer-api-external: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 7.935427ms
      message: 'load-balancer-api-external: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 5.024591ms
      message: 'load-balancer-api-external: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 10.031876ms
      message: 'load-balancer-api-external: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 4.248966ms
      message: 'load-balancer-api-external: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 9.376332ms
      message: 'load-balancer-api-external: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "56904"
    uid: 9ef1adae-6451-4610-bcc0-6dce3af3482a
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:22:27Z"
      message: 'load-balancer-api-internal: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.696954ms
      message: 'load-balancer-api-internal: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:27Z"
    - latency: 8.387269ms
      message: 'load-balancer-api-internal: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:46:27Z"
    - latency: 5.040463ms
      message: 'load-balancer-api-internal: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:27Z"
    - latency: 9.272088ms
      message: 'load-balancer-api-internal: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:45:27Z"
    - latency: 4.749762ms
      message: 'load-balancer-api-internal: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 7.859468ms
      message: 'load-balancer-api-internal: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 4.997277ms
      message: 'load-balancer-api-internal: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 10.06761ms
      message: 'load-balancer-api-internal: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 5.191284ms
      message: 'load-balancer-api-internal: tcp connection to a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 9.247085ms
      message: 'load-balancer-api-internal: resolved host name a3479645991a74323b920affbd88835c-ece471abcc0be81c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-132-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "55146"
    uid: b2a37098-7c72-4e77-bf52-47f1fadfe4a1
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:23:27Z"
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.411347ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 2.257456ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 2.202191ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 2.287022ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:27Z"
    - latency: 2.448848ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:27Z"
    - latency: 2.409003ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:27Z"
    - latency: 2.52123ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:38:27Z"
    - latency: 2.452856ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:37:27Z"
    - latency: 3.367307ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:36:27Z"
    - latency: 2.097104ms
      message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:35:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-136-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "55147"
    uid: ba626f92-3ca4-45b7-a772-7b5b1a3dd471
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:23:27Z"
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.380162ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 2.151265ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 2.286926ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 2.814284ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:27Z"
    - latency: 2.309388ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:27Z"
    - latency: 2.38726ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:27Z"
    - latency: 2.503223ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:38:27Z"
    - latency: 2.323835ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:37:27Z"
    - latency: 2.255402ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:36:27Z"
    - latency: 2.153976ms
      message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:35:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-138-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "55145"
    uid: c47085a9-b360-4c7a-93e9-67187479f2b5
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:23:27Z"
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.055µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 923.193µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 1.147409ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 1.105521ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:27Z"
    - latency: 1.282969ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:27Z"
    - latency: 1.31259ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:27Z"
    - latency: 1.377012ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:38:27Z"
    - latency: 1.328178ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:37:27Z"
    - latency: 1.011858ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:36:27Z"
    - latency: 1.00766ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:35:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: c5704d1c-2c3d-4b28-b9d7-9f4a470b0d3e
    resourceVersion: "56902"
    uid: 2330b47e-954d-4d4d-a10b-48c2a2f1e72e
  spec:
    sourcePod: network-check-source-685456655f-9zwfw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:22:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:27Z"
    - latency: 2.047585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:46:27Z"
    - latency: 1.154193ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:27Z"
    - latency: 1.976299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:45:27Z"
    - latency: 1.38062ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 2.380145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:44:27Z"
    - latency: 1.11371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 2.021296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:43:27Z"
    - latency: 1.073621ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:27Z"
    - latency: 2.032402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:42:27Z"
kind: List
metadata:
  resourceVersion: ""