apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "88661"
    uid: 96ecae1d-fa5b-441f-9189-3a140640db33
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:48:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.237993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:37:08Z"
    - latency: 1.363503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:36:08Z"
    - latency: 1.30423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 1.590133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 1.334426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 836.24µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 969.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 1.18866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:30:08Z"
    - latency: 925.935µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:29:08Z"
    - latency: 1.281852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:28:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "87189"
    uid: 74dad4b6-53ec-4398-824c-321df18b86c5
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:47:08Z"
      message: 'load-balancer-api-external: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.981742ms
      message: 'load-balancer-api-external: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 6.979103ms
      message: 'load-balancer-api-external: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 52.137275ms
      message: 'load-balancer-api-external: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 6.802824ms
      message: 'load-balancer-api-external: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 52.772267ms
      message: 'load-balancer-api-external: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 6.58966ms
      message: 'load-balancer-api-external: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 54.382459ms
      message: 'load-balancer-api-external: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 6.54665ms
      message: 'load-balancer-api-external: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 55.118416ms
      message: 'load-balancer-api-external: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 9.005268ms
      message: 'load-balancer-api-external: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:31:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "87190"
    uid: 90a644a2-7896-4b5b-a8f4-fe3a19bf64fe
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:47:08Z"
      message: 'load-balancer-api-internal: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.925231ms
      message: 'load-balancer-api-internal: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 7.031394ms
      message: 'load-balancer-api-internal: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 52.089246ms
      message: 'load-balancer-api-internal: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 6.879111ms
      message: 'load-balancer-api-internal: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 52.794685ms
      message: 'load-balancer-api-internal: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 6.534213ms
      message: 'load-balancer-api-internal: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 53.396243ms
      message: 'load-balancer-api-internal: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 6.576789ms
      message: 'load-balancer-api-internal: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 55.151297ms
      message: 'load-balancer-api-internal: tcp connection to a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 9.049257ms
      message: 'load-balancer-api-internal: resolved host name a0165055bbafc464b85f5db0d8234891-51f743d41745d646.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:31:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-128-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "88659"
    uid: cf53c902-6e0d-4f1f-a6b7-8425bb49ad3e
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:48:08Z"
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.928638ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:37:08Z"
    - latency: 2.176264ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:36:08Z"
    - latency: 2.143598ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 1.821704ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 2.107333ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 1.916766ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 2.246126ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 1.897773ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:30:08Z"
    - latency: 1.768828ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:29:08Z"
    - latency: 2.012292ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:28:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-141-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "88657"
    uid: 5e8ae183-6d2e-40a9-ae7e-84bf59b88247
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:48:08Z"
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.240249ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:37:08Z"
    - latency: 2.201425ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:36:08Z"
    - latency: 1.073266ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 937.764µs
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 1.456817ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 1.154475ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 819.606µs
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 1.305889ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:30:08Z"
    - latency: 1.161371ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:29:08Z"
    - latency: 986.837µs
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:28:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-142-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "88658"
    uid: f852e475-40e7-4150-ad2e-627b31f28530
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:48:08Z"
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.222049ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:37:08Z"
    - latency: 2.547908ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:36:08Z"
    - latency: 2.281362ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 2.015741ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 2.39813ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 1.941651ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 1.934046ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 2.493775ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:30:08Z"
    - latency: 1.994557ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:29:08Z"
    - latency: 2.116275ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:28:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:41:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.us-west-1.compute.internal
      uid: 06b9d68c-76c3-4746-abcf-3c54e19dc5a6
    resourceVersion: "87187"
    uid: 4e1105ad-1b98-42d8-9ee0-286a18aba28a
  spec:
    sourcePod: network-check-source-6f78d59f99-f6gzh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:47:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.664µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 2.048962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:35:08Z"
    - latency: 902.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 1.947721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:34:08Z"
    - latency: 906.384µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 1.960622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:33:08Z"
    - latency: 888.605µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 1.895854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:32:08Z"
    - latency: 844.545µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:31:08Z"
    - latency: 2.793991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T21:31:08Z"
kind: List
metadata:
  resourceVersion: ""