apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53894"
    uid: 5f109d7c-74f8-4f4e-a678-8a3f3b52afde
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:11: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.384179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 851.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 1.074241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 1.501931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 1.449996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 897.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:23:26Z"
    - latency: 1.023442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:22:26Z"
    - latency: 1.045379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:21:26Z"
    - latency: 1.205399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:20:26Z"
    - latency: 1.163655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:19:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53896"
    uid: 809f9cef-35c6-4e40-a3c3-753634bf21e0
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:10:26Z"
      message: 'load-balancer-api-external: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.687271ms
      message: 'load-balancer-api-external: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 7.447072ms
      message: 'load-balancer-api-external: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 4.526181ms
      message: 'load-balancer-api-external: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 8.359099ms
      message: 'load-balancer-api-external: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 5.14064ms
      message: 'load-balancer-api-external: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 8.695664ms
      message: 'load-balancer-api-external: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 4.453023ms
      message: 'load-balancer-api-external: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 7.054889ms
      message: 'load-balancer-api-external: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 5.031998ms
      message: 'load-balancer-api-external: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 8.186758ms
      message: 'load-balancer-api-external: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53895"
    uid: 074c4546-6436-44b6-958d-d17703263aab
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:10:26Z"
      message: 'load-balancer-api-internal: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.726804ms
      message: 'load-balancer-api-internal: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 7.410943ms
      message: 'load-balancer-api-internal: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 5.153755ms
      message: 'load-balancer-api-internal: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 8.257987ms
      message: 'load-balancer-api-internal: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 5.118805ms
      message: 'load-balancer-api-internal: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 8.731214ms
      message: 'load-balancer-api-internal: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 4.442287ms
      message: 'load-balancer-api-internal: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 6.933399ms
      message: 'load-balancer-api-internal: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 4.570054ms
      message: 'load-balancer-api-internal: tcp connection to af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 8.158174ms
      message: 'load-balancer-api-internal: resolved host name af06eb13d92a14283a281040b8dd32ab-b908795bf9b3068a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-142-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53890"
    uid: b75d9f80-ae1f-440a-b2ab-61a6e8e9e0bf
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:11:26Z"
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.84µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 1.046744ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 784.519µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 902.432µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 908.047µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 849.82µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:23:26Z"
    - latency: 846.786µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:22:26Z"
    - latency: 1.224028ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:21:26Z"
    - latency: 1.49618ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:20:26Z"
    - latency: 966.421µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:19:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-142-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53891"
    uid: cf2cf98c-46d7-46cb-887e-4c77e3eac841
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:11:26Z"
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.932185ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 2.014052ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 1.875143ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 1.944178ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 1.841752ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 2.007418ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:23:26Z"
    - latency: 2.091179ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:22:26Z"
    - latency: 1.965385ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:21:26Z"
    - latency: 2.020916ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:20:26Z"
    - latency: 1.931698ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:19:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-143-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53892"
    uid: 309fc907-04fe-48e5-8e71-518546768774
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:11:26Z"
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.984108ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 2.16528ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 2.317301ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 2.159355ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 2.409827ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 2.037091ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:23:26Z"
    - latency: 2.498725ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:22:26Z"
    - latency: 2.426118ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:21:26Z"
    - latency: 2.288731ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:20:26Z"
    - latency: 2.413478ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:19:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T17:04:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.ec2.internal
      uid: 251dee92-e9dc-407b-a69a-ddf64d5d27d6
    resourceVersion: "53893"
    uid: 0b9efc7a-4647-4702-b650-ba53aecf25dc
  spec:
    sourcePod: network-check-source-7d88cb55d8-v72rf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T17:10:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095868ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 1.696568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:28:26Z"
    - latency: 898.982µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 1.837544ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:27:26Z"
    - latency: 1.114758ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 2.142831ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:26:26Z"
    - latency: 954.824µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 1.712044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:25:26Z"
    - latency: 1.33615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T18:24:26Z"
    - latency: 1.832791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T18:24:26Z"
kind: List
metadata:
  resourceVersion: ""