apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "187155"
    uid: 413ec6b2-402e-4e1f-8aab-1c564db506e5
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:57:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.441268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:53:37Z"
    - latency: 1.275144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:52:37Z"
    - latency: 1.103744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:51:37Z"
    - latency: 1.344442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 1.504471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 1.157618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 1.10365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 1.370477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 1.224196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:45:37Z"
    - latency: 1.015883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:44:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "184164"
    uid: d1738399-f3dc-4302-a7f3-6876c6027fd5
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:56:37Z"
      message: 'load-balancer-api-external: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.926244ms
      message: 'load-balancer-api-external: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 6.826575ms
      message: 'load-balancer-api-external: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 5.434098ms
      message: 'load-balancer-api-external: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 7.717634ms
      message: 'load-balancer-api-external: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 5.731813ms
      message: 'load-balancer-api-external: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 9.657486ms
      message: 'load-balancer-api-external: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 4.521972ms
      message: 'load-balancer-api-external: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 5.900474ms
      message: 'load-balancer-api-external: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 6.174296ms
      message: 'load-balancer-api-external: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 8.282726ms
      message: 'load-balancer-api-external: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:46:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "184163"
    uid: 5a439a70-c987-468e-b296-bda485726130
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:56:37Z"
      message: 'load-balancer-api-internal: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.937163ms
      message: 'load-balancer-api-internal: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 6.729735ms
      message: 'load-balancer-api-internal: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 5.455397ms
      message: 'load-balancer-api-internal: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 7.649015ms
      message: 'load-balancer-api-internal: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 5.743267ms
      message: 'load-balancer-api-internal: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 9.635584ms
      message: 'load-balancer-api-internal: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 4.498669ms
      message: 'load-balancer-api-internal: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 5.96835ms
      message: 'load-balancer-api-internal: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 14.125838ms
      message: 'load-balancer-api-internal: tcp connection to afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 8.190783ms
      message: 'load-balancer-api-internal: resolved host name afffbf848a78a420593d2fcf8918689f-ea78c1a58b5fd16e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:46:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-128-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "187153"
    uid: 53d35f13-122d-41c6-b8bb-b9852d614212
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:57:37Z"
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.236464ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:53:37Z"
    - latency: 2.287998ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:52:37Z"
    - latency: 2.410252ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:51:37Z"
    - latency: 2.579384ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 7.134974ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 2.105387ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 2.303913ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 2.429328ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 2.870501ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:45:37Z"
    - latency: 2.457907ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:44:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-141-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "187154"
    uid: 17a47237-fcb7-49e2-9976-a8cf599ef8f9
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:57:37Z"
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206426ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:53:37Z"
    - latency: 2.108058ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:52:37Z"
    - latency: 2.182192ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:51:37Z"
    - latency: 2.237463ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 2.211127ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 2.182887ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 1.821588ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 2.039018ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 2.158327ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:45:37Z"
    - latency: 2.043768ms
      message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:44:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-143-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "187152"
    uid: 8b80b5b1-47fa-4865-b4fb-d3ba43f80d1b
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:57:37Z"
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.29299ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:53:37Z"
    - latency: 1.247324ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:52:37Z"
    - latency: 1.350546ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:51:37Z"
    - latency: 1.682467ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 1.652184ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 1.331553ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 1.310405ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 976.703µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 1.042307ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:45:37Z"
    - latency: 1.546977ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:44:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T15:50:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.us-east-2.compute.internal
      uid: 7e93fe4c-6628-4c97-82fb-1363d0bc62ea
    resourceVersion: "184162"
    uid: 48e01c4e-82e6-4945-9a59-796dec6ab43f
  spec:
    sourcePod: network-check-source-6f78d59f99-9bwcj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T15:56:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 1.817178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:50:37Z"
    - latency: 942.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 2.379398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:49:37Z"
    - latency: 920.898µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 1.919696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:48:37Z"
    - latency: 942.06µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 1.76525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:47:37Z"
    - latency: 798.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T16:46:37Z"
    - latency: 2.042773ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T16:46:37Z"
kind: List
metadata:
  resourceVersion: ""