apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "91798"
    uid: 6ded8432-d449-4af7-b173-907998f9f382
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.470544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 997.392µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:22Z"
    - latency: 841.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:22Z"
    - latency: 1.189623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:22Z"
    - latency: 1.530713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:22Z"
    - latency: 786.766µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:22Z"
    - latency: 1.123933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:22Z"
    - latency: 1.332986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:22Z"
    - latency: 9.136567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:22Z"
    - latency: 1.084948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "94873"
    uid: a1868ec9-0379-48d8-a47d-ec149a237034
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:44:22Z"
      message: 'load-balancer-api-external: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 49.162504ms
      message: 'load-balancer-api-external: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:22Z"
    - latency: 6.858567ms
      message: 'load-balancer-api-external: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:22Z"
    - latency: 53.946787ms
      message: 'load-balancer-api-external: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:22Z"
    - latency: 7.206771ms
      message: 'load-balancer-api-external: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:22Z"
    - latency: 56.18011ms
      message: 'load-balancer-api-external: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:22Z"
    - latency: 7.718193ms
      message: 'load-balancer-api-external: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:22Z"
    - latency: 51.650525ms
      message: 'load-balancer-api-external: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:22Z"
    - latency: 6.38296ms
      message: 'load-balancer-api-external: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:35:22Z"
    - latency: 49.917051ms
      message: 'load-balancer-api-external: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 6.887186ms
      message: 'load-balancer-api-external: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "94874"
    uid: 48b881bc-3280-4f56-9d16-fbf2f2c739bf
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:44:22Z"
      message: 'load-balancer-api-internal: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.732648ms
      message: 'load-balancer-api-internal: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:22Z"
    - latency: 6.910854ms
      message: 'load-balancer-api-internal: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:22Z"
    - latency: 54.82021ms
      message: 'load-balancer-api-internal: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:22Z"
    - latency: 7.241816ms
      message: 'load-balancer-api-internal: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:22Z"
    - latency: 56.183609ms
      message: 'load-balancer-api-internal: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:22Z"
    - latency: 7.637965ms
      message: 'load-balancer-api-internal: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:22Z"
    - latency: 51.674189ms
      message: 'load-balancer-api-internal: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:22Z"
    - latency: 6.434332ms
      message: 'load-balancer-api-internal: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:35:22Z"
    - latency: 50.412501ms
      message: 'load-balancer-api-internal: tcp connection to a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 6.783117ms
      message: 'load-balancer-api-internal: resolved host name a511c06f6c4c24b5eb9148195e6ce288-46029cde054419ce.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:34:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-network-check-target-ip-10-0-128-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "91797"
    uid: e3266fad-cbd4-4a7a-8b7f-5e091002ee8e
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:22Z"
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.339709ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 2.064194ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:22Z"
    - latency: 2.117119ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:22Z"
    - latency: 2.381501ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:22Z"
    - latency: 2.159151ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:22Z"
    - latency: 2.203102ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:22Z"
    - latency: 2.502479ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:22Z"
    - latency: 2.015747ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:22Z"
    - latency: 9.459416ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:22Z"
    - latency: 2.44409ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-network-check-target-ip-10-0-131-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "91795"
    uid: 3b8ec50c-2e3b-4de1-ac8e-c18d34136c59
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:22Z"
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.216587ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 1.306981ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:22Z"
    - latency: 1.025398ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:22Z"
    - latency: 898.489µs
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:22Z"
    - latency: 1.533863ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:22Z"
    - latency: 1.272997ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:22Z"
    - latency: 819.629µs
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:22Z"
    - latency: 885.647µs
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:22Z"
    - latency: 10.198062ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:22Z"
    - latency: 1.006608ms
      message: 'network-check-target-ip-10-0-131-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-network-check-target-ip-10-0-140-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "91796"
    uid: 995501d1-6763-4596-8e36-a57f90628894
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:22Z"
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.675421ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 2.285472ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:22Z"
    - latency: 2.285305ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:22Z"
    - latency: 2.383628ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:22Z"
    - latency: 2.254936ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:22Z"
    - latency: 2.287617ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:22Z"
    - latency: 2.416847ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:22Z"
    - latency: 2.242147ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:22Z"
    - latency: 16.98418ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:22Z"
    - latency: 2.346552ms
      message: 'network-check-target-ip-10-0-140-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-224-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-224.us-west-2.compute.internal
      uid: e874655f-d30d-4891-a941-fd56d2475097
    resourceVersion: "94871"
    uid: 1a6f1a20-6795-45c9-b6f1-0836df7a8cda
  spec:
    sourcePod: network-check-source-6f78d59f99-fswdh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:44:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.272547ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:22Z"
    - latency: 1.946445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:22Z"
    - latency: 1.034946ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:22Z"
    - latency: 2.030966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:22Z"
    - latency: 977.303µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:22Z"
    - latency: 2.04593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:22Z"
    - latency: 898.518µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:22Z"
    - latency: 1.769151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:35:22Z"
    - latency: 965.362µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:22Z"
    - latency: 1.958093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:34:22Z"
kind: List
metadata:
  resourceVersion: ""