apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "53679"
    uid: c2fb30de-d467-4c15-828b-66183ef92ab8
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:16:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.812µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 1.014121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 1.296469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 912.45µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:48Z"
    - latency: 821.492µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:48Z"
    - latency: 1.331574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:48Z"
    - latency: 836.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:48Z"
    - latency: 1.086424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:48Z"
    - latency: 997.224µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:48Z"
    - latency: 1.307221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "55138"
    uid: 20f3e272-0a8d-48bc-8453-4dab6e4f0ca0
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:15:48Z"
      message: 'load-balancer-api-external: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.237435ms
      message: 'load-balancer-api-external: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:39:48Z"
    - latency: 8.39298ms
      message: 'load-balancer-api-external: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:39:48Z"
    - latency: 3.642176ms
      message: 'load-balancer-api-external: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:38:48Z"
    - latency: 9.437715ms
      message: 'load-balancer-api-external: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:38:48Z"
    - latency: 4.968684ms
      message: 'load-balancer-api-external: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 10.29498ms
      message: 'load-balancer-api-external: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 4.856915ms
      message: 'load-balancer-api-external: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 8.324372ms
      message: 'load-balancer-api-external: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 5.321604ms
      message: 'load-balancer-api-external: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 10.271954ms
      message: 'load-balancer-api-external: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:35:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "55137"
    uid: f892a990-99eb-40b0-a33b-fce2bf925025
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:15:48Z"
      message: 'load-balancer-api-internal: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.272317ms
      message: 'load-balancer-api-internal: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:39:48Z"
    - latency: 8.437738ms
      message: 'load-balancer-api-internal: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:39:48Z"
    - latency: 3.658695ms
      message: 'load-balancer-api-internal: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:38:48Z"
    - latency: 9.478076ms
      message: 'load-balancer-api-internal: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:38:48Z"
    - latency: 4.846728ms
      message: 'load-balancer-api-internal: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 10.235274ms
      message: 'load-balancer-api-internal: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 4.866465ms
      message: 'load-balancer-api-internal: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 8.168079ms
      message: 'load-balancer-api-internal: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 5.338243ms
      message: 'load-balancer-api-internal: tcp connection to af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 11.066245ms
      message: 'load-balancer-api-internal: resolved host name af8eee50ce7be4940a082bf9554c4827-9e5117b1a4dca35e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:35:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-137-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "53676"
    uid: 006efa6a-ff08-40e4-a3e4-b1d25c30f25a
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:16:48Z"
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0152ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 822.807µs
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 1.151422ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 1.382908ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:48Z"
    - latency: 1.596504ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:48Z"
    - latency: 1.124832ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:48Z"
    - latency: 1.191247ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:48Z"
    - latency: 919.121µs
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:48Z"
    - latency: 1.0375ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:48Z"
    - latency: 1.865568ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-137-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "53677"
    uid: e4300fb8-f6bf-434b-a760-31d9730adbeb
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:16:48Z"
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.851672ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 2.358064ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 1.978097ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 2.221577ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:48Z"
    - latency: 2.885429ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:48Z"
    - latency: 2.248154ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:48Z"
    - latency: 2.296768ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:48Z"
    - latency: 2.158228ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:48Z"
    - latency: 2.130172ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:48Z"
    - latency: 2.611123ms
      message: 'network-check-target-ip-10-0-137-25: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-143-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "53678"
    uid: 297a5a72-6ea5-494b-8072-20407879f685
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:16:48Z"
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.267808ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 2.072938ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 2.572643ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 2.235524ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:34:48Z"
    - latency: 2.326433ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:33:48Z"
    - latency: 2.577055ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:32:48Z"
    - latency: 2.423025ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:31:48Z"
    - latency: 2.53504ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:30:48Z"
    - latency: 2.13087ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:29:48Z"
    - latency: 2.478129ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:28:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T22:09:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 10626829-a760-472a-a596-12723e094f50
    resourceVersion: "55136"
    uid: bb052133-fd5b-4311-9889-b03f63681610
  spec:
    sourcePod: network-check-source-6f8b768455-mcmvz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T22:15:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.376µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:39:48Z"
    - latency: 1.721052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:39:48Z"
    - latency: 1.154529ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:38:48Z"
    - latency: 1.683404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:38:48Z"
    - latency: 928.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 1.892924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:37:48Z"
    - latency: 1.121974ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 1.958607ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:36:48Z"
    - latency: 922.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T22:35:48Z"
    - latency: 1.256439ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T22:35:48Z"
kind: List
metadata:
  resourceVersion: ""