apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "54476"
    uid: 58930dfa-668c-42e0-873a-2e388625c114
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 1.08805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 977.905µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 1.15891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:48Z"
    - latency: 1.471903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:48Z"
    - latency: 1.197564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:48Z"
    - latency: 1.054811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:48Z"
    - latency: 1.264177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:48Z"
    - latency: 1.28968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:48Z"
    - latency: 1.155086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:48:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "56145"
    uid: 9bc7e5aa-cc11-4439-b30f-27891ce09415
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:35:48Z"
      message: 'load-balancer-api-external: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.787279ms
      message: 'load-balancer-api-external: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:59:48Z"
    - latency: 6.562472ms
      message: 'load-balancer-api-external: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:59:48Z"
    - latency: 4.62863ms
      message: 'load-balancer-api-external: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:48Z"
    - latency: 6.930362ms
      message: 'load-balancer-api-external: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:58:48Z"
    - latency: 4.468294ms
      message: 'load-balancer-api-external: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 7.723984ms
      message: 'load-balancer-api-external: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 4.350708ms
      message: 'load-balancer-api-external: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 7.026432ms
      message: 'load-balancer-api-external: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 3.519323ms
      message: 'load-balancer-api-external: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 9.014553ms
      message: 'load-balancer-api-external: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:55:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "56146"
    uid: 7e60fac3-29b5-4310-8ae2-2c9c55b8e556
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:35:48Z"
      message: 'load-balancer-api-internal: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.704095ms
      message: 'load-balancer-api-internal: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:59:48Z"
    - latency: 6.47329ms
      message: 'load-balancer-api-internal: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:59:48Z"
    - latency: 4.960115ms
      message: 'load-balancer-api-internal: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:48Z"
    - latency: 6.904573ms
      message: 'load-balancer-api-internal: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:58:48Z"
    - latency: 4.477191ms
      message: 'load-balancer-api-internal: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 7.652948ms
      message: 'load-balancer-api-internal: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 4.375176ms
      message: 'load-balancer-api-internal: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 6.983646ms
      message: 'load-balancer-api-internal: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 4.878872ms
      message: 'load-balancer-api-internal: tcp connection to a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 8.997464ms
      message: 'load-balancer-api-internal: resolved host name a0ef36a2aa03544bd81d5ca6ffaadd89-a687463c307ce165.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:55:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-network-check-target-ip-10-0-128-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "54473"
    uid: b7e2eca6-95f1-4f9b-8e93-fe5f93608cb3
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:48Z"
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.412466ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 1.013073ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 1.014386ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 1.067075ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:48Z"
    - latency: 1.064431ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:48Z"
    - latency: 1.158469ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:48Z"
    - latency: 1.035258ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:48Z"
    - latency: 1.012359ms
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:48Z"
    - latency: 981.548µs
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:48Z"
    - latency: 998.258µs
      message: 'network-check-target-ip-10-0-128-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:48:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-network-check-target-ip-10-0-130-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "54474"
    uid: 609573f3-59b1-4f3a-b934-684415b43af1
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:48Z"
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.240908ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 2.296601ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 2.562784ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 2.51475ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:48Z"
    - latency: 2.687893ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:48Z"
    - latency: 2.611311ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:48Z"
    - latency: 2.700913ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:48Z"
    - latency: 2.49178ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:48Z"
    - latency: 2.574626ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:48Z"
    - latency: 2.489263ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:48:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-network-check-target-ip-10-0-141-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "54475"
    uid: c7136a56-3142-49d1-8e55-1a55c3b3e176
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:36:48Z"
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.167698ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 2.423593ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 2.601986ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 2.394017ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:54:48Z"
    - latency: 2.234786ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:53:48Z"
    - latency: 3.210905ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:52:48Z"
    - latency: 2.192436ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:51:48Z"
    - latency: 2.429756ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:50:48Z"
    - latency: 2.420857ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:49:48Z"
    - latency: 2.553915ms
      message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:48:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T06:29:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-174-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-174.ec2.internal
      uid: 496756ba-9cd6-4be8-89a1-eb817cd54545
    resourceVersion: "56144"
    uid: dbdc2675-457e-4fbf-8767-9d34867de925
  spec:
    sourcePod: network-check-source-685456655f-c9dt2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T06:35:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.114µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:59:48Z"
    - latency: 1.613586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:59:48Z"
    - latency: 1.022644ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:58:48Z"
    - latency: 1.739123ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:58:48Z"
    - latency: 1.054395ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 2.031376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:57:48Z"
    - latency: 925.514µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 1.747105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:56:48Z"
    - latency: 1.138701ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T06:55:48Z"
    - latency: 1.823877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T06:55:48Z"
kind: List
metadata:
  resourceVersion: ""