apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "84880"
    uid: 742eebce-05eb-4717-8f5e-a0853f23c00f
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:27:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 1.087795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 1.252352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:30Z"
    - latency: 948.643µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:20:30Z"
    - latency: 1.144373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:19:30Z"
    - latency: 1.000151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:18:30Z"
    - latency: 939.453µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:17:30Z"
    - latency: 843.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:16:30Z"
    - latency: 1.0982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:15:30Z"
    - latency: 1.527981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:14:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "87547"
    uid: a2644786-8682-4a28-a242-0caf9a3ab4b3
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:26:30Z"
      message: 'load-balancer-api-external: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.789351ms
      message: 'load-balancer-api-external: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:30Z"
    - latency: 8.443686ms
      message: 'load-balancer-api-external: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:26:30Z"
    - latency: 4.763524ms
      message: 'load-balancer-api-external: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:30Z"
    - latency: 8.362841ms
      message: 'load-balancer-api-external: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:25:30Z"
    - latency: 4.549098ms
      message: 'load-balancer-api-external: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:30Z"
    - latency: 9.223801ms
      message: 'load-balancer-api-external: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:24:30Z"
    - latency: 4.158866ms
      message: 'load-balancer-api-external: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 8.620017ms
      message: 'load-balancer-api-external: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 4.580286ms
      message: 'load-balancer-api-external: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 8.159418ms
      message: 'load-balancer-api-external: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:22:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "87548"
    uid: d087c7f2-6555-4a59-84bd-bcbb57146844
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:26:30Z"
      message: 'load-balancer-api-internal: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.447085ms
      message: 'load-balancer-api-internal: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:30Z"
    - latency: 8.408345ms
      message: 'load-balancer-api-internal: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:26:30Z"
    - latency: 3.107672ms
      message: 'load-balancer-api-internal: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:30Z"
    - latency: 8.394064ms
      message: 'load-balancer-api-internal: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:25:30Z"
    - latency: 4.522403ms
      message: 'load-balancer-api-internal: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:30Z"
    - latency: 9.243037ms
      message: 'load-balancer-api-internal: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:24:30Z"
    - latency: 6.043295ms
      message: 'load-balancer-api-internal: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 8.686346ms
      message: 'load-balancer-api-internal: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 4.585053ms
      message: 'load-balancer-api-internal: tcp connection to a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 8.105493ms
      message: 'load-balancer-api-internal: resolved host name a2433f0f09ff14f239a2b7e2f9ebd7e7-336254b3d25a4427.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:22:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-ip-10-0-128-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "84878"
    uid: c5e6ee6d-3eae-4aa6-83d8-838697c42a3a
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:27:30Z"
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.469486ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 2.151697ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 2.437534ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:30Z"
    - latency: 2.45613ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:20:30Z"
    - latency: 2.655626ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:19:30Z"
    - latency: 2.943298ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:18:30Z"
    - latency: 2.418227ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:17:30Z"
    - latency: 2.245398ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:16:30Z"
    - latency: 2.666767ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:15:30Z"
    - latency: 2.195889ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:14:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-ip-10-0-130-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "84879"
    uid: 2f9cf313-46e8-403a-8ba1-5b9122373a21
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:27:30Z"
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.094756ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 2.511141ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 2.417309ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:30Z"
    - latency: 2.429086ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:20:30Z"
    - latency: 2.498146ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:19:30Z"
    - latency: 2.285808ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:18:30Z"
    - latency: 2.136635ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:17:30Z"
    - latency: 2.637879ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:16:30Z"
    - latency: 2.423778ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:15:30Z"
    - latency: 3.199562ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:14:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-ip-10-0-132-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "84877"
    uid: a903cbdd-1a81-4119-8664-a4479f7e5e2f
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:27:30Z"
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.133752ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 1.196134ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 1.040732ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:30Z"
    - latency: 1.382729ms
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:20:30Z"
    - latency: 899.783µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:19:30Z"
    - latency: 896.696µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:18:30Z"
    - latency: 792.194µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:17:30Z"
    - latency: 783.98µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:16:30Z"
    - latency: 738.772µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:15:30Z"
    - latency: 877.618µs
      message: 'network-check-target-ip-10-0-132-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:14:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-254.ec2.internal
      uid: 041dc335-10d9-4bb9-9052-28733631f541
    resourceVersion: "87546"
    uid: 39cc2a09-617d-49fa-be6f-996307bc49ab
  spec:
    sourcePod: network-check-source-685456655f-bqkz9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:26:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.397619ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:30Z"
    - latency: 1.644472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:26:30Z"
    - latency: 1.055176ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:30Z"
    - latency: 1.927754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:25:30Z"
    - latency: 952.734µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:30Z"
    - latency: 1.757918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:24:30Z"
    - latency: 1.202595ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 1.909875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:23:30Z"
    - latency: 859.2µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:30Z"
    - latency: 1.85125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:22:30Z"
kind: List
metadata:
  resourceVersion: ""