apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "43402"
    uid: ac9d07a5-d072-4050-b446-48d6fc5516ff
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:05:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 1.015041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 1.049092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 1.115133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:23:41Z"
    - latency: 1.109168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:22:41Z"
    - latency: 1.405447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:21:41Z"
    - latency: 2.029827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:20:41Z"
    - latency: 1.077434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:19:41Z"
    - latency: 1.467826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:18:41Z"
    - latency: 1.250939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:17:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "45627"
    uid: 6f9d51a3-0887-4d3d-925e-3961791dca06
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:04:41Z"
      message: 'load-balancer-api-external: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.140116ms
      message: 'load-balancer-api-external: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:28:41Z"
    - latency: 7.245148ms
      message: 'load-balancer-api-external: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:28:41Z"
    - latency: 4.954037ms
      message: 'load-balancer-api-external: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:27:41Z"
    - latency: 6.504016ms
      message: 'load-balancer-api-external: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:27:41Z"
    - latency: 4.125403ms
      message: 'load-balancer-api-external: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 8.653898ms
      message: 'load-balancer-api-external: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 4.335677ms
      message: 'load-balancer-api-external: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 6.411617ms
      message: 'load-balancer-api-external: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 4.296104ms
      message: 'load-balancer-api-external: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 12.803948ms
      message: 'load-balancer-api-external: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:24:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "45626"
    uid: d7b01aa7-0a52-4b62-96fa-a207804c24fb
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:04:41Z"
      message: 'load-balancer-api-internal: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.468991ms
      message: 'load-balancer-api-internal: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:28:41Z"
    - latency: 7.284974ms
      message: 'load-balancer-api-internal: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:28:41Z"
    - latency: 4.896816ms
      message: 'load-balancer-api-internal: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:27:41Z"
    - latency: 6.535801ms
      message: 'load-balancer-api-internal: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:27:41Z"
    - latency: 4.857513ms
      message: 'load-balancer-api-internal: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 8.863974ms
      message: 'load-balancer-api-internal: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 4.321422ms
      message: 'load-balancer-api-internal: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 6.469938ms
      message: 'load-balancer-api-internal: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 3.77408ms
      message: 'load-balancer-api-internal: tcp connection to a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 12.832683ms
      message: 'load-balancer-api-internal: resolved host name a46b8b04419774a42a664e6123fb1ca6-40f2e7e433f9655a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:24:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-network-check-target-ip-10-0-137-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "43401"
    uid: 051d6c4c-5d03-4a85-aa57-efda9ef52179
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:05:41Z"
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.597106ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 2.534288ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 2.481488ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 2.421105ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:23:41Z"
    - latency: 2.490862ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:22:41Z"
    - latency: 2.440698ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:21:41Z"
    - latency: 2.316289ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:20:41Z"
    - latency: 2.23825ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:19:41Z"
    - latency: 2.7847ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:18:41Z"
    - latency: 2.367955ms
      message: 'network-check-target-ip-10-0-137-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:17:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-network-check-target-ip-10-0-137-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "43400"
    uid: 74c7f598-3bac-445c-8b44-cdadf46cd180
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:05:41Z"
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.037416ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 2.037563ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 2.133829ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 1.94206ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:23:41Z"
    - latency: 2.618485ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:22:41Z"
    - latency: 1.938942ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:21:41Z"
    - latency: 2.351113ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:20:41Z"
    - latency: 1.958494ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:19:41Z"
    - latency: 2.193446ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:18:41Z"
    - latency: 1.965617ms
      message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:17:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-network-check-target-ip-10-0-143-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "43399"
    uid: f97357e9-5e28-4669-bbcf-eec218439111
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:05:41Z"
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.073402ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 811.256µs
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 1.622099ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 947.314µs
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:23:41Z"
    - latency: 1.688757ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:22:41Z"
    - latency: 982.863µs
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:21:41Z"
    - latency: 1.638879ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:20:41Z"
    - latency: 1.459722ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:19:41Z"
    - latency: 902.439µs
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:18:41Z"
    - latency: 1.433469ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:17:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:58:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-65.ec2.internal
      uid: c4763ae0-3227-4209-a8a3-87f5335b979f
    resourceVersion: "45624"
    uid: 6a02d74f-c73a-4f5a-a0cf-fe1c7c8d4b20
  spec:
    sourcePod: network-check-source-7f44b6dd87-lqm57
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T15:04:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 718.229µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:28:41Z"
    - latency: 2.52606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:28:41Z"
    - latency: 1.034561ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:27:41Z"
    - latency: 1.830045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:27:41Z"
    - latency: 799.208µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 1.856791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:26:41Z"
    - latency: 1.054808ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 1.849158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:25:41Z"
    - latency: 824.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T15:24:41Z"
    - latency: 2.153993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T15:24:41Z"
kind: List
metadata:
  resourceVersion: ""