apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "37860"
    uid: bd0d2645-d310-410b-b274-89397eaaa3df
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:19:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.131293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:33:26Z"
    - latency: 1.281874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:32:26Z"
    - latency: 998.873µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:31:26Z"
    - latency: 1.020558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 1.255822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 1.001814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 1.333144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 1.045092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 746.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:25:26Z"
    - latency: 1.21458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "34642"
    uid: 1e381d2f-ad02-4ad6-8ed3-8ebd11080fb8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:18:26Z"
      message: 'load-balancer-api-external: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.812543ms
      message: 'load-balancer-api-external: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 7.47328ms
      message: 'load-balancer-api-external: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 4.354791ms
      message: 'load-balancer-api-external: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 7.127951ms
      message: 'load-balancer-api-external: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 4.465075ms
      message: 'load-balancer-api-external: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 6.877476ms
      message: 'load-balancer-api-external: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 4.518431ms
      message: 'load-balancer-api-external: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 6.776758ms
      message: 'load-balancer-api-external: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 4.60829ms
      message: 'load-balancer-api-external: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 7.193351ms
      message: 'load-balancer-api-external: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "34643"
    uid: b159f602-08ef-4327-a7ac-c91cc26cb1bc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:18:26Z"
      message: 'load-balancer-api-internal: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.66867ms
      message: 'load-balancer-api-internal: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 7.584278ms
      message: 'load-balancer-api-internal: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 4.178027ms
      message: 'load-balancer-api-internal: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 7.185831ms
      message: 'load-balancer-api-internal: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 3.667425ms
      message: 'load-balancer-api-internal: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 6.937337ms
      message: 'load-balancer-api-internal: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 4.879296ms
      message: 'load-balancer-api-internal: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 6.869176ms
      message: 'load-balancer-api-internal: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 4.584433ms
      message: 'load-balancer-api-internal: tcp connection to ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 7.249105ms
      message: 'load-balancer-api-internal: resolved host name ad37bffe92b6e446191afa4f5e837199-eb206c321991f996.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-network-check-target-ip-10-0-137-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "37855"
    uid: 254bf108-16df-487f-94f1-26758910d700
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:19:26Z"
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.766µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:33:26Z"
    - latency: 1.209881ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:32:26Z"
    - latency: 801.329µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:31:26Z"
    - latency: 1.04854ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 761.366µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 1.476829ms
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 917.988µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 936.93µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 919.365µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:25:26Z"
    - latency: 900.903µs
      message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-network-check-target-ip-10-0-140-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "37858"
    uid: da49e79c-173a-4a25-b129-f362853c063b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:19:26Z"
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.888033ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:33:26Z"
    - latency: 2.131574ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:32:26Z"
    - latency: 1.97928ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:31:26Z"
    - latency: 3.99532ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 2.07294ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 2.096043ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 2.074678ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 2.384896ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 1.931185ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:25:26Z"
    - latency: 1.872379ms
      message: 'network-check-target-ip-10-0-140-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-network-check-target-ip-10-0-141-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "37857"
    uid: 29ff2031-3602-4945-80e7-3df448463e59
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:19:26Z"
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.930707ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:33:26Z"
    - latency: 2.134735ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:32:26Z"
    - latency: 1.911194ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:31:26Z"
    - latency: 1.882782ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 1.629809ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 2.05807ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 2.091839ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 1.859205ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 1.80589ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:25:26Z"
    - latency: 1.659751ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T02:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-128.ec2.internal
      uid: cfd29c94-c16b-4ad4-8270-3aed1c291e25
    resourceVersion: "34641"
    uid: 18e30d92-0eb6-4a45-a6d1-65f1b985d846
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8s7vw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T02:18:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 847.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 1.932601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:30:26Z"
    - latency: 966.917µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 2.023167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:29:26Z"
    - latency: 1.325498ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 1.564089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:28:26Z"
    - latency: 886.423µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 1.731032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:27:26Z"
    - latency: 1.169145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:26:26Z"
    - latency: 1.805894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:26:26Z"
kind: List
metadata:
  resourceVersion: ""