apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80081"
    uid: db9a1243-9729-40cd-8c89-51a2986c2a00
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:44:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 1.111229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 1.189925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 1.199117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 1.061774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:50:45Z"
    - latency: 1.458264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:49:45Z"
    - latency: 961.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:48:45Z"
    - latency: 956.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:47:45Z"
    - latency: 1.052236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:46:45Z"
    - latency: 1.01709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:45:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80681"
    uid: 1f04383f-d939-45b3-b4ba-130d91f9f357
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:43:45Z"
      message: 'load-balancer-api-external: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.308337ms
      message: 'load-balancer-api-external: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:55:45Z"
    - latency: 7.207318ms
      message: 'load-balancer-api-external: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:55:45Z"
    - latency: 5.382186ms
      message: 'load-balancer-api-external: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 7.094546ms
      message: 'load-balancer-api-external: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 3.724431ms
      message: 'load-balancer-api-external: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 8.938464ms
      message: 'load-balancer-api-external: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 6.106152ms
      message: 'load-balancer-api-external: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 10.619694ms
      message: 'load-balancer-api-external: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 5.478029ms
      message: 'load-balancer-api-external: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 7.307134ms
      message: 'load-balancer-api-external: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:51:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80682"
    uid: 0acc93db-dbbd-4c78-8de3-0f13b28858fb
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:43:45Z"
      message: 'load-balancer-api-internal: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.699221ms
      message: 'load-balancer-api-internal: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:55:45Z"
    - latency: 7.117623ms
      message: 'load-balancer-api-internal: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:55:45Z"
    - latency: 5.382165ms
      message: 'load-balancer-api-internal: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 7.1506ms
      message: 'load-balancer-api-internal: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 3.717837ms
      message: 'load-balancer-api-internal: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 8.999228ms
      message: 'load-balancer-api-internal: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 7.097607ms
      message: 'load-balancer-api-internal: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 10.584366ms
      message: 'load-balancer-api-internal: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 5.398569ms
      message: 'load-balancer-api-internal: tcp connection to a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 7.277989ms
      message: 'load-balancer-api-internal: resolved host name a943d576bb3374d21a46773ce0e41ed6-04a49dcb808c47e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:51:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-network-check-target-ip-10-0-128-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80080"
    uid: c41257af-00aa-48ec-b8e7-69f253889065
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:44:45Z"
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.202384ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 2.247655ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 2.214044ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 2.432023ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 2.510447ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:50:45Z"
    - latency: 1.922885ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:49:45Z"
    - latency: 2.201981ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:48:45Z"
    - latency: 2.132785ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:47:45Z"
    - latency: 2.513537ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:46:45Z"
    - latency: 2.142269ms
      message: 'network-check-target-ip-10-0-128-170: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:45:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-network-check-target-ip-10-0-129-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80079"
    uid: 172e1b1a-7643-4192-ba0e-5c4b96d6dcd9
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:44:45Z"
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.97923ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 2.290439ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 2.193806ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 2.426954ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 2.555143ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:50:45Z"
    - latency: 2.244641ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:49:45Z"
    - latency: 2.136928ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:48:45Z"
    - latency: 2.178007ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:47:45Z"
    - latency: 2.444684ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:46:45Z"
    - latency: 2.501232ms
      message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:45:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-network-check-target-ip-10-0-132-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80078"
    uid: 83b21ae7-d63f-4caa-91a4-300c5cabe54c
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:44:45Z"
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.573µs
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 1.536627ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 1.023282ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 1.744868ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 1.409812ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:50:45Z"
    - latency: 1.766666ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:49:45Z"
    - latency: 1.530569ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:48:45Z"
    - latency: 1.004122ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:47:45Z"
    - latency: 1.005233ms
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:46:45Z"
    - latency: 984.284µs
      message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:45:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T09:37:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-105.ec2.internal
      uid: d64fbe51-3c92-4bd9-9662-a581fa518a64
    resourceVersion: "80680"
    uid: d7e9931a-f966-4728-b60d-d40e882fcde1
  spec:
    sourcePod: network-check-source-989f8b8dc-6fsgb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T09:43:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:55:45Z"
    - latency: 1.906974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:55:45Z"
    - latency: 1.157694ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 2.194098ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:54:45Z"
    - latency: 875.352µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 1.83841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:53:45Z"
    - latency: 1.041642ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 2.089785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:52:45Z"
    - latency: 1.054163ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T10:51:45Z"
    - latency: 2.16152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T10:51:45Z"
kind: List
metadata:
  resourceVersion: ""