apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62793"
    uid: 0eb34b6e-ec71-4345-a534-1edf0875917f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:30:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.22761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 924.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 1.026886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 1.267018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 1.284735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 1.327061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:00:39Z"
    - latency: 1.253772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:59:39Z"
    - latency: 1.221697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:58:39Z"
    - latency: 1.191319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:57:39Z"
    - latency: 2.563732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:56:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62796"
    uid: 3b4c378b-798a-4c5d-b712-e52ab9ee4138
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:29:40Z"
      message: 'load-balancer-api-external: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.628243ms
      message: 'load-balancer-api-external: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 7.328194ms
      message: 'load-balancer-api-external: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 5.106467ms
      message: 'load-balancer-api-external: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 11.22732ms
      message: 'load-balancer-api-external: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 4.359478ms
      message: 'load-balancer-api-external: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 6.361158ms
      message: 'load-balancer-api-external: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 8.786483ms
      message: 'load-balancer-api-external: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 10.445927ms
      message: 'load-balancer-api-external: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 5.480703ms
      message: 'load-balancer-api-external: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 8.215545ms
      message: 'load-balancer-api-external: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62795"
    uid: 33561c1a-fbd5-4924-9d30-60ac2927f487
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:29:39Z"
      message: 'load-balancer-api-internal: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.660217ms
      message: 'load-balancer-api-internal: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 7.390303ms
      message: 'load-balancer-api-internal: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 5.169977ms
      message: 'load-balancer-api-internal: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 11.281009ms
      message: 'load-balancer-api-internal: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 4.367973ms
      message: 'load-balancer-api-internal: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 6.306263ms
      message: 'load-balancer-api-internal: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 4.01955ms
      message: 'load-balancer-api-internal: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 10.49427ms
      message: 'load-balancer-api-internal: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 5.312436ms
      message: 'load-balancer-api-internal: tcp connection to a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 8.290425ms
      message: 'load-balancer-api-internal: resolved host name a4531ea4de1eb4f7494ea6858ebefd1d-6a6f32eb2d45c69a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-network-check-target-ip-10-0-132-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62791"
    uid: 53f8d8e7-19ca-4906-8138-d900676261e0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:30:39Z"
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175428ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 1.839241ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 2.084876ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 2.035628ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 1.843738ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 2.844527ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:00:39Z"
    - latency: 2.230348ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:59:39Z"
    - latency: 2.330875ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:58:39Z"
    - latency: 2.185438ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:57:39Z"
    - latency: 2.49524ms
      message: 'network-check-target-ip-10-0-132-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:56:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-network-check-target-ip-10-0-141-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62789"
    uid: 7ae6ac91-ef34-48cd-a839-94430d6a4ac1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:30:39Z"
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.655µs
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 870.428µs
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 1.076955ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 1.468201ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 1.052324ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 1.152696ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:00:39Z"
    - latency: 1.597204ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:59:39Z"
    - latency: 1.368029ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:58:39Z"
    - latency: 2.111072ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:57:39Z"
    - latency: 1.261704ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:56:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-network-check-target-ip-10-0-142-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62790"
    uid: 6cd25a2a-a1b0-432f-99b1-28b2c088984d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:30:39Z"
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.000146ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 1.931563ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 2.332015ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 2.390834ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 1.823189ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 2.799724ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:00:39Z"
    - latency: 1.837889ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:59:39Z"
    - latency: 3.463924ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:58:39Z"
    - latency: 2.25917ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:57:39Z"
    - latency: 2.989169ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:56:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:23:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-54.ec2.internal
      uid: a79b0775-f9d9-4c53-93a1-bfc6c5f4dfe2
    resourceVersion: "62792"
    uid: c181b29a-a79f-4433-9d59-11b17f4dd83c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-q77w8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:29:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.168µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 2.177227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:05:39Z"
    - latency: 848.463µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 1.899166ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:04:39Z"
    - latency: 954.108µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 1.81075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:03:39Z"
    - latency: 886.33µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 1.981894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:02:39Z"
    - latency: 1.016244ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:01:39Z"
    - latency: 1.990662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:01:39Z"
kind: List
metadata:
  resourceVersion: ""