apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68010"
    uid: 201df35f-f4b6-4466-bd66-1f6782f5560f
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.318961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 1.055587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 1.298146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 894.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 1.100517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:25Z"
    - latency: 976.716µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:25Z"
    - latency: 1.018636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:25Z"
    - latency: 1.206256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:25Z"
    - latency: 976.766µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:25Z"
    - latency: 1.149564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:13:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68974"
    uid: da2e550a-d2c6-4a81-90cc-1351361133d3
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:53:25Z"
      message: 'load-balancer-api-external: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.456796ms
      message: 'load-balancer-api-external: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:25Z"
    - latency: 8.272328ms
      message: 'load-balancer-api-external: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:23:25Z"
    - latency: 3.6902ms
      message: 'load-balancer-api-external: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 9.144724ms
      message: 'load-balancer-api-external: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 5.866945ms
      message: 'load-balancer-api-external: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 7.730209ms
      message: 'load-balancer-api-external: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 4.474366ms
      message: 'load-balancer-api-external: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 7.766822ms
      message: 'load-balancer-api-external: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 3.248903ms
      message: 'load-balancer-api-external: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 8.605077ms
      message: 'load-balancer-api-external: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:19:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68975"
    uid: 75443b04-8ae9-40d5-b957-70883cfaa2ec
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:53:25Z"
      message: 'load-balancer-api-internal: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.413676ms
      message: 'load-balancer-api-internal: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:25Z"
    - latency: 8.201378ms
      message: 'load-balancer-api-internal: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:23:25Z"
    - latency: 5.144449ms
      message: 'load-balancer-api-internal: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 9.074605ms
      message: 'load-balancer-api-internal: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 4.718494ms
      message: 'load-balancer-api-internal: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 7.64491ms
      message: 'load-balancer-api-internal: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 4.460008ms
      message: 'load-balancer-api-internal: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 7.692366ms
      message: 'load-balancer-api-internal: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 3.25715ms
      message: 'load-balancer-api-internal: tcp connection to a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 8.629957ms
      message: 'load-balancer-api-internal: resolved host name a73678053d394412c9a6393e6e2a0707-fe2eb62d49e3a723.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:19:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-network-check-target-ip-10-0-136-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68009"
    uid: 33a45d6f-d526-439d-98b1-10585412b458
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:25Z"
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.846133ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 2.57002ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 2.538045ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 2.596917ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 2.293102ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:25Z"
    - latency: 2.569441ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:25Z"
    - latency: 2.445934ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:25Z"
    - latency: 2.76395ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:25Z"
    - latency: 2.576548ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:25Z"
    - latency: 2.777727ms
      message: 'network-check-target-ip-10-0-136-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:13:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-network-check-target-ip-10-0-141-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68007"
    uid: 1aa45fef-8321-4812-a508-d281ba19501d
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:25Z"
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072544ms
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 1.02914ms
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 1.471622ms
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 881.163µs
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 926.695µs
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:25Z"
    - latency: 922.887µs
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:25Z"
    - latency: 1.159371ms
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:25Z"
    - latency: 912.975µs
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:25Z"
    - latency: 1.352952ms
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:25Z"
    - latency: 1.331154ms
      message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:13:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-network-check-target-ip-10-0-143-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68008"
    uid: 02037255-a22f-42bd-ab3b-f4ed5de9fb14
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:25Z"
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.268286ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 2.563284ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 2.665343ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 2.256407ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 2.476478ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:25Z"
    - latency: 2.733272ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:25Z"
    - latency: 2.424899ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:25Z"
    - latency: 2.372121ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:25Z"
    - latency: 2.807165ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:25Z"
    - latency: 2.659948ms
      message: 'network-check-target-ip-10-0-143-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:13:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:47:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-222.ec2.internal
      uid: 9ca48749-26c8-4049-82c8-6e9dcaca70e4
    resourceVersion: "68972"
    uid: d7b2d377-c18f-43f3-aecb-9812d84ddb77
  spec:
    sourcePod: network-check-source-7cbc45fddc-fvx98
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:53:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:25Z"
    - latency: 1.811239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:23:25Z"
    - latency: 871.744µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 2.026524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:22:25Z"
    - latency: 946.125µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 2.244562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:21:25Z"
    - latency: 872.163µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 1.700238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:20:25Z"
    - latency: 943.927µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:25Z"
    - latency: 1.922583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:19:25Z"
kind: List
metadata:
  resourceVersion: ""