apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31461"
    uid: 605f5bb4-26d7-49a8-bce3-5a94ce0117ce
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.35µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 904.921µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 1.227624ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 817.617µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 955.053µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 777.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:25Z"
    - latency: 767.221µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:25Z"
    - latency: 1.156383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:34:25Z"
    - latency: 853.208µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:33:25Z"
    - latency: 834.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:32:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31462"
    uid: 804212b0-43f0-4551-ba03-b3a27dcd4e23
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:25Z"
      message: 'load-balancer-api-external: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.00328ms
      message: 'load-balancer-api-external: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 9.039409ms
      message: 'load-balancer-api-external: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 4.329016ms
      message: 'load-balancer-api-external: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 7.535792ms
      message: 'load-balancer-api-external: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 6.295905ms
      message: 'load-balancer-api-external: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 8.0997ms
      message: 'load-balancer-api-external: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 6.111488ms
      message: 'load-balancer-api-external: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 8.708854ms
      message: 'load-balancer-api-external: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 4.48696ms
      message: 'load-balancer-api-external: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 6.778488ms
      message: 'load-balancer-api-external: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:37:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31464"
    uid: d7b74bba-5770-4baa-be9f-4553bb582851
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:25Z"
      message: 'load-balancer-api-internal: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.860587ms
      message: 'load-balancer-api-internal: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 9.108559ms
      message: 'load-balancer-api-internal: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 5.176776ms
      message: 'load-balancer-api-internal: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 7.624776ms
      message: 'load-balancer-api-internal: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 6.297434ms
      message: 'load-balancer-api-internal: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 8.146955ms
      message: 'load-balancer-api-internal: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 3.943517ms
      message: 'load-balancer-api-internal: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 8.763113ms
      message: 'load-balancer-api-internal: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 5.19855ms
      message: 'load-balancer-api-internal: tcp connection to a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 6.869668ms
      message: 'load-balancer-api-internal: resolved host name a20f59d4ee05543f69000d2beb2a27aa-561b488962ba67b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:37:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-network-check-target-ip-10-0-128-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31457"
    uid: 5189165e-facf-47bf-8db6-cd7f90d00825
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:25Z"
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.65µs
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 1.016577ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 752.574µs
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 1.48998ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 778.797µs
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 795.899µs
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:25Z"
    - latency: 867.475µs
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:25Z"
    - latency: 1.420428ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:34:25Z"
    - latency: 879.725µs
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:33:25Z"
    - latency: 1.615242ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:32:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-network-check-target-ip-10-0-140-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31458"
    uid: 528b0888-988d-4c3c-97eb-d7c2d534f71b
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:25Z"
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.184035ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 2.104806ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 2.158518ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 2.544769ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 2.496864ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 2.100457ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:25Z"
    - latency: 1.90641ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:25Z"
    - latency: 2.189847ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:34:25Z"
    - latency: 2.180702ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:33:25Z"
    - latency: 2.308371ms
      message: 'network-check-target-ip-10-0-140-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:32:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-network-check-target-ip-10-0-143-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31459"
    uid: e4094146-b420-4d68-be52-a1e595ca9814
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:25Z"
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.246422ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 2.103558ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 2.264612ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 2.219581ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 2.075742ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 2.215444ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:25Z"
    - latency: 2.259157ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:25Z"
    - latency: 2.18785ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:34:25Z"
    - latency: 2.153768ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:33:25Z"
    - latency: 2.478702ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:32:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-222.ec2.internal
      uid: d99cdd22-6e9a-494f-b795-de4c96c48f86
    resourceVersion: "31460"
    uid: ddc41e9a-f9c9-45db-899e-cdffc5da8024
  spec:
    sourcePod: network-check-source-7cbc45fddc-pnkdl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.998µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 1.77864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:41:25Z"
    - latency: 1.095707ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 1.562561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:40:25Z"
    - latency: 710.469µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 1.634014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:39:25Z"
    - latency: 874.942µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 2.015532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:38:25Z"
    - latency: 1.259892ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:25Z"
    - latency: 1.777967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:37:25Z"
kind: List
metadata:
  resourceVersion: ""