apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "54879"
    uid: 2073def0-24a9-4af3-89dd-00eea824b74c
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:33:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.061µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 1.010057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 1.738656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 923.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 924.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:57:10Z"
    - latency: 905.288µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:56:10Z"
    - latency: 1.375482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:55:10Z"
    - latency: 1.178454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:54:10Z"
    - latency: 1.152073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:53:10Z"
    - latency: 1.157369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:52:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "55830"
    uid: ec47f693-3f3d-4c7e-bc88-1b03e10b9430
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:32:10Z"
      message: 'load-balancer-api-external: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.485995ms
      message: 'load-balancer-api-external: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:02:10Z"
    - latency: 8.433802ms
      message: 'load-balancer-api-external: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:02:10Z"
    - latency: 4.677372ms
      message: 'load-balancer-api-external: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 7.508832ms
      message: 'load-balancer-api-external: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 3.7834ms
      message: 'load-balancer-api-external: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 9.014197ms
      message: 'load-balancer-api-external: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 5.360636ms
      message: 'load-balancer-api-external: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 8.404113ms
      message: 'load-balancer-api-external: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 5.420992ms
      message: 'load-balancer-api-external: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 6.694107ms
      message: 'load-balancer-api-external: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:58:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "55829"
    uid: 8820dd6a-42ee-4203-8a85-8ab3c2a4ef77
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:32:10Z"
      message: 'load-balancer-api-internal: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.499138ms
      message: 'load-balancer-api-internal: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:02:10Z"
    - latency: 8.42053ms
      message: 'load-balancer-api-internal: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:02:10Z"
    - latency: 4.630938ms
      message: 'load-balancer-api-internal: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 7.538763ms
      message: 'load-balancer-api-internal: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 3.827941ms
      message: 'load-balancer-api-internal: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 8.977758ms
      message: 'load-balancer-api-internal: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 4.040686ms
      message: 'load-balancer-api-internal: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 8.34824ms
      message: 'load-balancer-api-internal: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 11.223694ms
      message: 'load-balancer-api-internal: tcp connection to a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 6.677305ms
      message: 'load-balancer-api-internal: resolved host name a4d35e74d798c48d19e963c8896e1b14-4cafef94302539ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:58:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-network-check-target-ip-10-0-129-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "54878"
    uid: b44c9eb5-c698-4259-9954-bb39a4188cbc
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:33:10Z"
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.207228ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 2.800698ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 2.640499ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 2.151409ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 2.240511ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:57:10Z"
    - latency: 2.699901ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:56:10Z"
    - latency: 2.239174ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:55:10Z"
    - latency: 2.763538ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:54:10Z"
    - latency: 2.588125ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:53:10Z"
    - latency: 2.371336ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:52:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-network-check-target-ip-10-0-136-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "54877"
    uid: eca86dc3-5898-489b-8390-cf8c5f5b07b2
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:33:10Z"
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.016373ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 2.601008ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 2.532343ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 2.299389ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 2.093851ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:57:10Z"
    - latency: 2.016395ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:56:10Z"
    - latency: 2.454042ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:55:10Z"
    - latency: 2.432232ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:54:10Z"
    - latency: 2.557803ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:53:10Z"
    - latency: 2.430226ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:52:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-network-check-target-ip-10-0-138-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "54876"
    uid: 70b47cf1-5f45-4d1c-b2a1-3d524147af9e
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:33:10Z"
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.322857ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 1.519913ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 908.197µs
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 1.239759ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 954.61µs
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:57:10Z"
    - latency: 1.070654ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:56:10Z"
    - latency: 1.109436ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:55:10Z"
    - latency: 1.018241ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:54:10Z"
    - latency: 968.093µs
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:53:10Z"
    - latency: 1.003444ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:52:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:26:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-192-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-192.ec2.internal
      uid: 23a06a14-5bea-43e7-8c1c-ab7f8f9a14a2
    resourceVersion: "55828"
    uid: 18b7c2f0-9511-42c3-8237-eb4feb1edfec
  spec:
    sourcePod: network-check-source-989f8b8dc-mqkx8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:32:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.195195ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:02:10Z"
    - latency: 1.775493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:02:10Z"
    - latency: 1.057409ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 1.784198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:01:10Z"
    - latency: 920.628µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 1.701298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T13:00:10Z"
    - latency: 943.199µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 2.088577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:59:10Z"
    - latency: 840.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:58:10Z"
    - latency: 1.58498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:58:10Z"
kind: List
metadata:
  resourceVersion: ""