apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "199662"
    uid: 091a650a-4139-40c6-a680-3d2f484632f5
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:33:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.190143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:57:15Z"
    - latency: 1.234319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:56:15Z"
    - latency: 1.30569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:55:15Z"
    - latency: 1.04248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:54:15Z"
    - latency: 1.223684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:53:15Z"
    - latency: 1.200481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:52:15Z"
    - latency: 1.640807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:51:15Z"
    - latency: 969.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:50:15Z"
    - latency: 938.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:15Z"
    - latency: 1.256572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "203672"
    uid: 010dcf8e-93f9-422e-90a1-9b3585cd8038
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:32:15Z"
      message: 'load-balancer-api-external: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.092453ms
      message: 'load-balancer-api-external: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:02:15Z"
    - latency: 7.77583ms
      message: 'load-balancer-api-external: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:02:15Z"
    - latency: 15.531536ms
      message: 'load-balancer-api-external: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:01:15Z"
    - latency: 9.212187ms
      message: 'load-balancer-api-external: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:01:15Z"
    - latency: 16.236812ms
      message: 'load-balancer-api-external: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:00:15Z"
    - latency: 8.18371ms
      message: 'load-balancer-api-external: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:00:15Z"
    - latency: 17.506938ms
      message: 'load-balancer-api-external: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:59:15Z"
    - latency: 7.064445ms
      message: 'load-balancer-api-external: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:59:15Z"
    - latency: 14.358315ms
      message: 'load-balancer-api-external: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:58:15Z"
    - latency: 6.801086ms
      message: 'load-balancer-api-external: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:58:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "203673"
    uid: 2cbfb745-303e-425d-b227-f92dc8e6ed9d
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:32:15Z"
      message: 'load-balancer-api-internal: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.183016ms
      message: 'load-balancer-api-internal: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:02:15Z"
    - latency: 7.88493ms
      message: 'load-balancer-api-internal: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:02:15Z"
    - latency: 15.06769ms
      message: 'load-balancer-api-internal: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:01:15Z"
    - latency: 9.299366ms
      message: 'load-balancer-api-internal: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:01:15Z"
    - latency: 17.183641ms
      message: 'load-balancer-api-internal: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:00:15Z"
    - latency: 8.242509ms
      message: 'load-balancer-api-internal: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:00:15Z"
    - latency: 17.565613ms
      message: 'load-balancer-api-internal: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:59:15Z"
    - latency: 7.158507ms
      message: 'load-balancer-api-internal: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:59:15Z"
    - latency: 15.164777ms
      message: 'load-balancer-api-internal: tcp connection to a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:58:15Z"
    - latency: 6.766634ms
      message: 'load-balancer-api-internal: resolved host name a5866f36015a441789d207334e161f19-59b11cdbe4a5ccd6.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:58:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-network-check-target-ip-10-0-134-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "199659"
    uid: ff1771c7-87e2-498c-80c4-85eabee19522
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:33:15Z"
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.484µs
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:57:15Z"
    - latency: 840.162µs
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:56:15Z"
    - latency: 1.372157ms
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:55:15Z"
    - latency: 1.206374ms
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:54:15Z"
    - latency: 925.15µs
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:53:15Z"
    - latency: 948.887µs
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:52:15Z"
    - latency: 1.684995ms
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:51:15Z"
    - latency: 1.121692ms
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:50:15Z"
    - latency: 1.712996ms
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:15Z"
    - latency: 935.218µs
      message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-network-check-target-ip-10-0-135-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "199660"
    uid: 7b0f2530-bf47-46f7-a7f3-cd3c27a43cf8
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:33:15Z"
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.208682ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:57:15Z"
    - latency: 2.216911ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:56:15Z"
    - latency: 2.010976ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:55:15Z"
    - latency: 2.62728ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:54:15Z"
    - latency: 2.096609ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:53:15Z"
    - latency: 2.159401ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:52:15Z"
    - latency: 2.243571ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:51:15Z"
    - latency: 2.008529ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:50:15Z"
    - latency: 2.018829ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:15Z"
    - latency: 2.191602ms
      message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-network-check-target-ip-10-0-137-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "199661"
    uid: 84019e3b-24cb-42c3-9660-4e4a94ee8257
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:33:15Z"
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.570892ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:57:15Z"
    - latency: 2.422786ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:56:15Z"
    - latency: 2.220407ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:55:15Z"
    - latency: 2.668471ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:54:15Z"
    - latency: 2.119887ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:53:15Z"
    - latency: 2.593586ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:52:15Z"
    - latency: 3.033655ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:51:15Z"
    - latency: 2.359472ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:50:15Z"
    - latency: 2.38699ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:15Z"
    - latency: 2.318631ms
      message: 'network-check-target-ip-10-0-137-156: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T07:26:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-79.ec2.internal
      uid: ac528d09-c618-46c0-afc4-7b6a30fd9246
    resourceVersion: "203670"
    uid: 07acccd9-656e-4e69-a3eb-910295aebb16
  spec:
    sourcePod: network-check-source-6f78d59f99-lrtvc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T07:32:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.03µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:02:15Z"
    - latency: 2.152844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:02:15Z"
    - latency: 990.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:01:15Z"
    - latency: 2.434025ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:01:15Z"
    - latency: 809.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T09:00:15Z"
    - latency: 2.367018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T09:00:15Z"
    - latency: 811.436µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:59:15Z"
    - latency: 1.839254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:59:15Z"
    - latency: 1.169812ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:58:15Z"
    - latency: 2.058251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:58:15Z"
kind: List
metadata:
  resourceVersion: ""