apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61856"
    uid: 257107b8-1d0f-4029-ac6c-bf63f54c4186
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:27:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 814.853µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 832.616µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 1.03266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 994.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 843.648µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:57:53Z"
    - latency: 788.902µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:56:53Z"
    - latency: 1.355645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:55:53Z"
    - latency: 875.516µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:54:53Z"
    - latency: 916.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61858"
    uid: 67c828f7-bdef-4149-9fce-17b18aae1c63
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:26:53Z"
      message: 'load-balancer-api-external: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.958009ms
      message: 'load-balancer-api-external: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 8.440849ms
      message: 'load-balancer-api-external: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 5.626901ms
      message: 'load-balancer-api-external: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 8.673904ms
      message: 'load-balancer-api-external: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 4.816126ms
      message: 'load-balancer-api-external: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 8.200174ms
      message: 'load-balancer-api-external: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 5.916192ms
      message: 'load-balancer-api-external: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 9.976691ms
      message: 'load-balancer-api-external: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 4.329846ms
      message: 'load-balancer-api-external: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 7.48827ms
      message: 'load-balancer-api-external: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:58:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61857"
    uid: 34df6068-8692-45f3-9250-c9c9d700de95
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:26:53Z"
      message: 'load-balancer-api-internal: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.994371ms
      message: 'load-balancer-api-internal: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 8.398737ms
      message: 'load-balancer-api-internal: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 5.599107ms
      message: 'load-balancer-api-internal: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 8.722802ms
      message: 'load-balancer-api-internal: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 4.496664ms
      message: 'load-balancer-api-internal: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 8.251987ms
      message: 'load-balancer-api-internal: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 5.860239ms
      message: 'load-balancer-api-internal: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 10.032135ms
      message: 'load-balancer-api-internal: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 4.363424ms
      message: 'load-balancer-api-internal: tcp connection to a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 7.406508ms
      message: 'load-balancer-api-internal: resolved host name a6720f4fb6a884604866887de48dc774-7135d235da5f91a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:58:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-ip-10-0-129-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61853"
    uid: 4cc4c874-a56e-4341-80ea-2bd08b8300ba
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:27:53Z"
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275881ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 2.343409ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 2.400841ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 2.315207ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 2.334096ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 2.027704ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:57:53Z"
    - latency: 2.769231ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:56:53Z"
    - latency: 2.218867ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:55:53Z"
    - latency: 2.109543ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:54:53Z"
    - latency: 2.172316ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-ip-10-0-134-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61852"
    uid: 5dab645f-7256-4ac8-94c6-0c4e3502879a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:27:53Z"
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153347ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 1.257264ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 968.362µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 979.596µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 924.328µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 684.346µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:57:53Z"
    - latency: 747.22µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:56:53Z"
    - latency: 1.417909ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:55:53Z"
    - latency: 1.328379ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:54:53Z"
    - latency: 775.066µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-ip-10-0-140-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61854"
    uid: f435ccfa-aecd-4e63-9b92-44cfd9d48037
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:27:53Z"
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.380052ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 2.506499ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 2.485503ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 2.266284ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 2.296641ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 2.445121ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:57:53Z"
    - latency: 2.505166ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:56:53Z"
    - latency: 2.711519ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:55:53Z"
    - latency: 2.099314ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:54:53Z"
    - latency: 2.405753ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:53:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:20:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: a93b0d02-82bd-401c-8f90-a50c1371eaf4
    resourceVersion: "61855"
    uid: c89a6aaf-894a-4276-9374-f39ac32cec91
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hqml7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:26:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02462ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 1.939837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:02:53Z"
    - latency: 911.543µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 1.791441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:01:53Z"
    - latency: 1.118229ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 2.110715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:00:53Z"
    - latency: 863.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 1.737384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:59:53Z"
    - latency: 933.961µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:58:53Z"
    - latency: 1.540065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:58:53Z"
kind: List
metadata:
  resourceVersion: ""