apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "53630"
    uid: 1ec89055-4b9d-4960-821e-934e56a629a0
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:53:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.391029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 828.154µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 1.04688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 1.097019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 1.027637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:17:47Z"
    - latency: 1.114187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:16:47Z"
    - latency: 1.546128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:15:47Z"
    - latency: 1.85806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:14:47Z"
    - latency: 1.313402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:13:47Z"
    - latency: 1.428195ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "54965"
    uid: 951cd549-8cb3-45ad-b0e2-c8487c44959d
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:52:47Z"
      message: 'load-balancer-api-external: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.378546ms
      message: 'load-balancer-api-external: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:22:47Z"
    - latency: 6.657456ms
      message: 'load-balancer-api-external: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:22:47Z"
    - latency: 4.580837ms
      message: 'load-balancer-api-external: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 6.884809ms
      message: 'load-balancer-api-external: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 4.92226ms
      message: 'load-balancer-api-external: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 6.92051ms
      message: 'load-balancer-api-external: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 4.774948ms
      message: 'load-balancer-api-external: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 7.344741ms
      message: 'load-balancer-api-external: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 4.171185ms
      message: 'load-balancer-api-external: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 7.685516ms
      message: 'load-balancer-api-external: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "54964"
    uid: c5df4939-b158-4ba6-98ac-859892ac049f
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:52:47Z"
      message: 'load-balancer-api-internal: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.376173ms
      message: 'load-balancer-api-internal: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:22:47Z"
    - latency: 6.613507ms
      message: 'load-balancer-api-internal: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:22:47Z"
    - latency: 4.315141ms
      message: 'load-balancer-api-internal: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 6.835945ms
      message: 'load-balancer-api-internal: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 4.909649ms
      message: 'load-balancer-api-internal: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 6.863596ms
      message: 'load-balancer-api-internal: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 3.823054ms
      message: 'load-balancer-api-internal: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 7.293514ms
      message: 'load-balancer-api-internal: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 4.114345ms
      message: 'load-balancer-api-internal: tcp connection to a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 7.641799ms
      message: 'load-balancer-api-internal: resolved host name a8941e54df91c44a48d63b43b9d4c250-f6246b915032d589.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-network-check-target-ip-10-0-134-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "53628"
    uid: 3ed1ee9c-6c39-429d-812c-eeabf8d43eca
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:53:47Z"
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.180356ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 1.907021ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 2.128266ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 1.465175ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 1.998141ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:17:47Z"
    - latency: 1.970255ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:16:47Z"
    - latency: 1.936441ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:15:47Z"
    - latency: 2.247314ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:14:47Z"
    - latency: 2.021653ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:13:47Z"
    - latency: 1.97157ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-network-check-target-ip-10-0-136-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "53629"
    uid: dfe07c5c-969a-44dc-bc3e-7f76b94fb5c4
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:53:47Z"
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306601ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 2.205079ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 2.370111ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 1.983123ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 2.375443ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:17:47Z"
    - latency: 2.646061ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:16:47Z"
    - latency: 2.161069ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:15:47Z"
    - latency: 2.59259ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:14:47Z"
    - latency: 2.358645ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:13:47Z"
    - latency: 2.181012ms
      message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-network-check-target-ip-10-0-138-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "53627"
    uid: 9f9f0aff-168b-4e42-9b55-03e0da844942
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:53:47Z"
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.597801ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 912.73µs
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 1.601791ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 1.378874ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 1.477213ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:17:47Z"
    - latency: 1.381945ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:16:47Z"
    - latency: 1.289997ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:15:47Z"
    - latency: 2.0732ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:14:47Z"
    - latency: 1.04408ms
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:13:47Z"
    - latency: 885.141µs
      message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T01:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-104-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-104.ec2.internal
      uid: bb3089d0-9609-45e8-98dc-c7de46e9be84
    resourceVersion: "54963"
    uid: b20342b7-389e-4cdc-9040-f771bd94b730
  spec:
    sourcePod: network-check-source-989f8b8dc-lscpf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T01:52:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.57µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:22:47Z"
    - latency: 1.742954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:22:47Z"
    - latency: 815.045µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 2.155635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:21:47Z"
    - latency: 1.461374ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 1.695549ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:20:47Z"
    - latency: 880.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 1.946489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:19:47Z"
    - latency: 1.016822ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T02:18:47Z"
    - latency: 2.24472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T02:18:47Z"
kind: List
metadata:
  resourceVersion: ""