apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69444"
    uid: 4aa97eea-a080-4478-a461-b6dcaa84b09a
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:23:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.059187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 767.91µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 1.217703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 1.338265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 1.558604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 990.767µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:53:53Z"
    - latency: 959.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:52:53Z"
    - latency: 1.307752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:51:53Z"
    - latency: 1.477209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:50:53Z"
    - latency: 1.166813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:49:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69446"
    uid: 2adffb2f-8ec8-41a2-bcea-fd1b18e1120b
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:22:53Z"
      message: 'load-balancer-api-external: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.402885ms
      message: 'load-balancer-api-external: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 6.337481ms
      message: 'load-balancer-api-external: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 4.987566ms
      message: 'load-balancer-api-external: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 6.647288ms
      message: 'load-balancer-api-external: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 5.329828ms
      message: 'load-balancer-api-external: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 12.853163ms
      message: 'load-balancer-api-external: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 4.983551ms
      message: 'load-balancer-api-external: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 7.91398ms
      message: 'load-balancer-api-external: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 3.87716ms
      message: 'load-balancer-api-external: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 7.065759ms
      message: 'load-balancer-api-external: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:54:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69445"
    uid: 6ccc96cf-f894-4099-829f-f1a5f34d90f5
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:22:53Z"
      message: 'load-balancer-api-internal: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.361807ms
      message: 'load-balancer-api-internal: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 6.373791ms
      message: 'load-balancer-api-internal: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 5.001991ms
      message: 'load-balancer-api-internal: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 6.529719ms
      message: 'load-balancer-api-internal: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 5.722239ms
      message: 'load-balancer-api-internal: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 12.885654ms
      message: 'load-balancer-api-internal: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 4.96699ms
      message: 'load-balancer-api-internal: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 7.967933ms
      message: 'load-balancer-api-internal: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 4.417112ms
      message: 'load-balancer-api-internal: tcp connection to aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 6.928545ms
      message: 'load-balancer-api-internal: resolved host name aa38ef855833f4f8bb0e0d9453fb9dd4-95e66afdda398744.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:54:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-network-check-target-ip-10-0-129-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69441"
    uid: 619cb9d5-6a8a-464a-9a32-261cf157309c
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:23:53Z"
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.458837ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 2.252098ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 2.753091ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 2.861152ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 2.276865ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 2.676126ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:53:53Z"
    - latency: 2.763606ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:52:53Z"
    - latency: 2.434098ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:51:53Z"
    - latency: 2.609711ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:50:53Z"
    - latency: 2.496179ms
      message: 'network-check-target-ip-10-0-129-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:49:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-network-check-target-ip-10-0-130-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69440"
    uid: 820d0d65-7ba9-4746-8110-df44eb6fc83b
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:23:53Z"
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.500703ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 852.905µs
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 1.643723ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 1.551767ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 953.253µs
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 995.917µs
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:53:53Z"
    - latency: 1.090195ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:52:53Z"
    - latency: 1.295498ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:51:53Z"
    - latency: 1.149052ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:50:53Z"
    - latency: 1.036444ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:49:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-network-check-target-ip-10-0-139-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69442"
    uid: edfbe107-c75f-467f-9cfa-0d42c9f1bc5b
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:23:53Z"
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.443976ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 2.110345ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 2.353604ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 2.79796ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 2.743538ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 2.458847ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:53:53Z"
    - latency: 2.344609ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:52:53Z"
    - latency: 2.464002ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:51:53Z"
    - latency: 2.197533ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:50:53Z"
    - latency: 2.548319ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:49:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:16:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-52.ec2.internal
      uid: 18e0afd0-b13a-44a7-ae97-13bb8eafa73d
    resourceVersion: "69443"
    uid: 3b901f8c-cedd-439f-a05b-7697cbd37fa6
  spec:
    sourcePod: network-check-source-7cbc45fddc-b8cv4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:22:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.331644ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 1.879699ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:58:53Z"
    - latency: 1.264451ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 1.86044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:57:53Z"
    - latency: 946.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 2.292173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:56:53Z"
    - latency: 819.407µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 2.037411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:55:53Z"
    - latency: 1.118125ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:54:53Z"
    - latency: 1.877364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:54:53Z"
kind: List
metadata:
  resourceVersion: ""