apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "82431"
    uid: ca72b1f2-2387-4bf4-85b1-f3a8c898a422
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:30:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.170637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 1.497633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 1.060145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:24:37Z"
    - latency: 1.411198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:23:37Z"
    - latency: 1.026643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:37Z"
    - latency: 1.023015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:37Z"
    - latency: 1.283183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:37Z"
    - latency: 1.016267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:37Z"
    - latency: 1.078463ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:37Z"
    - latency: 1.685901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "85407"
    uid: f338b888-04ba-46ea-9268-bc38ad90b914
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:29:37Z"
      message: 'load-balancer-api-external: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.5355ms
      message: 'load-balancer-api-external: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:29:37Z"
    - latency: 6.873415ms
      message: 'load-balancer-api-external: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:29:37Z"
    - latency: 5.137351ms
      message: 'load-balancer-api-external: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:28:37Z"
    - latency: 12.926336ms
      message: 'load-balancer-api-external: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:28:37Z"
    - latency: 6.055765ms
      message: 'load-balancer-api-external: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:27:37Z"
    - latency: 6.935539ms
      message: 'load-balancer-api-external: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:27:37Z"
    - latency: 5.340463ms
      message: 'load-balancer-api-external: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 16.562667ms
      message: 'load-balancer-api-external: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 5.636311ms
      message: 'load-balancer-api-external: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 6.89218ms
      message: 'load-balancer-api-external: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "85408"
    uid: 141a007c-4a8f-4410-b6ca-04a5d8d4443e
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:29:37Z"
      message: 'load-balancer-api-internal: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.537827ms
      message: 'load-balancer-api-internal: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:29:37Z"
    - latency: 6.92277ms
      message: 'load-balancer-api-internal: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:29:37Z"
    - latency: 5.113446ms
      message: 'load-balancer-api-internal: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:28:37Z"
    - latency: 13.03403ms
      message: 'load-balancer-api-internal: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:28:37Z"
    - latency: 6.070015ms
      message: 'load-balancer-api-internal: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:27:37Z"
    - latency: 7.168575ms
      message: 'load-balancer-api-internal: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:27:37Z"
    - latency: 5.391511ms
      message: 'load-balancer-api-internal: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 15.905675ms
      message: 'load-balancer-api-internal: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 5.656932ms
      message: 'load-balancer-api-internal: tcp connection to aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 7.02175ms
      message: 'load-balancer-api-internal: resolved host name aad7e7a7c818b4c1794f70efa8acc7b7-b23b59c16cf96cc5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:25:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-ip-10-0-128-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "82428"
    uid: e4e53302-7fb7-4597-b5de-432a4c1a28a0
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:30:37Z"
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.774µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 1.059167ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 926.417µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:24:37Z"
    - latency: 1.723822ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:23:37Z"
    - latency: 1.043201ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:37Z"
    - latency: 1.008961ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:37Z"
    - latency: 1.019875ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:37Z"
    - latency: 1.278485ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:37Z"
    - latency: 1.168491ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:37Z"
    - latency: 936.396µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-ip-10-0-135-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "82430"
    uid: 157f88d0-78ce-4412-85ca-e70f03c49415
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:30:37Z"
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.21894ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 2.472596ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 2.285014ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:24:37Z"
    - latency: 2.720925ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:23:37Z"
    - latency: 2.246214ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:37Z"
    - latency: 2.355006ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:37Z"
    - latency: 2.478542ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:37Z"
    - latency: 2.154049ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:37Z"
    - latency: 2.189398ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:37Z"
    - latency: 2.32905ms
      message: 'network-check-target-ip-10-0-135-175: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-ip-10-0-141-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "82429"
    uid: c1458581-fa60-40e9-bbeb-26bad6a5e7d8
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:30:37Z"
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.223784ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 2.582106ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 2.167089ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:24:37Z"
    - latency: 2.327666ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:23:37Z"
    - latency: 2.458716ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:37Z"
    - latency: 2.198499ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:37Z"
    - latency: 2.149577ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:37Z"
    - latency: 2.147807ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:37Z"
    - latency: 2.168403ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:37Z"
    - latency: 2.397116ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:23:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 593fc12a-4f68-4d5f-ae51-7830a08a4993
    resourceVersion: "85406"
    uid: a8334860-bb60-4df3-965d-b73b27775240
  spec:
    sourcePod: network-check-source-6f8b768455-spghd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:29:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.44µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:29:37Z"
    - latency: 1.744206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:29:37Z"
    - latency: 982.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:28:37Z"
    - latency: 1.869948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:28:37Z"
    - latency: 815.607µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:27:37Z"
    - latency: 1.878104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:27:37Z"
    - latency: 1.281899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 4.33915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:26:37Z"
    - latency: 1.014962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:25:37Z"
    - latency: 1.822779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:25:37Z"
kind: List
metadata:
  resourceVersion: ""