apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "39781"
    uid: 194a480f-01e2-434f-84e8-e827bd109ff5
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:59:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:48:29Z"
    - latency: 887.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:47:29Z"
    - latency: 1.164497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 856.693µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 887.105µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 1.238825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 974.578µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 851.89µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:41:29Z"
    - latency: 1.359079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:40:29Z"
    - latency: 981.238µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "38707"
    uid: 9b5577c6-716f-4a2f-b04f-ffaf1c28ee96
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:58:29Z"
      message: 'load-balancer-api-external: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.553072ms
      message: 'load-balancer-api-external: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 9.074776ms
      message: 'load-balancer-api-external: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 4.636107ms
      message: 'load-balancer-api-external: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 8.647202ms
      message: 'load-balancer-api-external: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 4.623583ms
      message: 'load-balancer-api-external: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 6.724846ms
      message: 'load-balancer-api-external: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 4.438495ms
      message: 'load-balancer-api-external: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 8.508775ms
      message: 'load-balancer-api-external: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 5.296754ms
      message: 'load-balancer-api-external: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 8.993855ms
      message: 'load-balancer-api-external: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:42:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "38708"
    uid: add7ef1e-03df-45d4-b44f-99d7bfc26681
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:58:29Z"
      message: 'load-balancer-api-internal: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.625303ms
      message: 'load-balancer-api-internal: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 9.022826ms
      message: 'load-balancer-api-internal: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 5.085425ms
      message: 'load-balancer-api-internal: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 8.6769ms
      message: 'load-balancer-api-internal: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 4.622106ms
      message: 'load-balancer-api-internal: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 6.671635ms
      message: 'load-balancer-api-internal: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 4.44542ms
      message: 'load-balancer-api-internal: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 8.458461ms
      message: 'load-balancer-api-internal: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 5.302105ms
      message: 'load-balancer-api-internal: tcp connection to aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 8.912923ms
      message: 'load-balancer-api-internal: resolved host name aeef695d8512a4eefb6702bbf60ae897-ff862d4f98c00bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:42:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-ip-10-0-139-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "39779"
    uid: 43b54cb9-ead8-49d9-a0dc-0bc63c1bb64e
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:59:29Z"
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155987ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:48:29Z"
    - latency: 2.446845ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:47:29Z"
    - latency: 2.330061ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 2.204734ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 1.952215ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 2.222087ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 2.267605ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 2.44766ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:41:29Z"
    - latency: 2.205721ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:40:29Z"
    - latency: 2.070892ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-ip-10-0-140-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "39780"
    uid: fedd8296-380e-4de3-aad2-5f37b849a932
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:59:29Z"
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.373427ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:48:29Z"
    - latency: 2.259199ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:47:29Z"
    - latency: 2.293383ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 2.416693ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 2.1402ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 2.384591ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 2.02457ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 2.344182ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:41:29Z"
    - latency: 2.224326ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:40:29Z"
    - latency: 2.21592ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-ip-10-0-142-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "39778"
    uid: deffbfa0-f79a-4423-8fec-65ff5dace1dc
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:59:29Z"
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.528158ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:48:29Z"
    - latency: 1.417274ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:47:29Z"
    - latency: 1.267135ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 718.832µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 1.183733ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 926.473µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 781.099µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 1.243872ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:41:29Z"
    - latency: 858.496µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:40:29Z"
    - latency: 864.236µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: d0f9a221-c514-43dc-917c-559009772de6
    resourceVersion: "38706"
    uid: 27ee2f39-9a48-4199-8dee-2b31ca2a81f2
  spec:
    sourcePod: network-check-source-7b678d77c7-pk46g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:58:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 830.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 1.914958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:46:29Z"
    - latency: 764.997µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 1.623803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:45:29Z"
    - latency: 774.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 1.906556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:44:29Z"
    - latency: 1.188253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 1.634198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:43:29Z"
    - latency: 853.709µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T17:42:29Z"
    - latency: 1.653247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T17:42:29Z"
kind: List
metadata:
  resourceVersion: ""