apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "28567"
    uid: 195e4060-1e10-45a1-87a2-19d969e7e51b
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:05:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:12:29Z"
    - latency: 919.695µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:11:29Z"
    - latency: 996.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 1.340935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 1.096119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 1.163749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 1.193861ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 2.759063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:05:29Z"
    - latency: 1.022328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:04:29Z"
    - latency: 1.090699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:03:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "27333"
    uid: 462802d4-f443-404c-95b9-67ef417aa54c
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:04:29Z"
      message: 'load-balancer-api-external: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.352366ms
      message: 'load-balancer-api-external: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 9.159819ms
      message: 'load-balancer-api-external: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 5.779356ms
      message: 'load-balancer-api-external: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 9.232325ms
      message: 'load-balancer-api-external: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 3.735931ms
      message: 'load-balancer-api-external: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 8.098139ms
      message: 'load-balancer-api-external: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 4.134235ms
      message: 'load-balancer-api-external: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 8.459576ms
      message: 'load-balancer-api-external: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 3.625546ms
      message: 'load-balancer-api-external: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 7.707275ms
      message: 'load-balancer-api-external: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:06:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "27334"
    uid: 98f99fa6-2bde-47d5-b544-de3be71d4072
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:04:29Z"
      message: 'load-balancer-api-internal: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.371242ms
      message: 'load-balancer-api-internal: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 9.071118ms
      message: 'load-balancer-api-internal: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 5.782859ms
      message: 'load-balancer-api-internal: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 9.210346ms
      message: 'load-balancer-api-internal: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 4.244841ms
      message: 'load-balancer-api-internal: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 8.017604ms
      message: 'load-balancer-api-internal: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 4.127376ms
      message: 'load-balancer-api-internal: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 8.395449ms
      message: 'load-balancer-api-internal: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 3.654065ms
      message: 'load-balancer-api-internal: tcp connection to a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 7.691047ms
      message: 'load-balancer-api-internal: resolved host name a7e65abc2cf2640d0b1894613379b86d-a88054dce474a058.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:06:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-134-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "28565"
    uid: 1e9808da-82c4-4e89-8f41-e95ca4c955b2
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:05:29Z"
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211318ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:12:29Z"
    - latency: 2.03765ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:11:29Z"
    - latency: 2.441118ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 2.264806ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 1.908927ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 2.124945ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 1.994154ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 2.16922ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:05:29Z"
    - latency: 2.337083ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:04:29Z"
    - latency: 2.249847ms
      message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:03:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-134-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "28566"
    uid: ec504ae6-282c-42c1-8a06-cc501fb4fac4
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:05:29Z"
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066309ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:12:29Z"
    - latency: 2.20314ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:11:29Z"
    - latency: 2.956595ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 2.221438ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 1.975211ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 2.280128ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 2.920453ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 1.958265ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:05:29Z"
    - latency: 2.305768ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:04:29Z"
    - latency: 2.244528ms
      message: 'network-check-target-ip-10-0-134-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:03:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-136-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "28564"
    uid: fbcb451b-5efd-4f7c-8428-ea62ee8c1630
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:05:29Z"
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 849.149µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:12:29Z"
    - latency: 799.35µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:11:29Z"
    - latency: 2.132669ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 947.655µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 826.104µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 1.144815ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 1.169909ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 3.45597ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:05:29Z"
    - latency: 851.186µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:04:29Z"
    - latency: 1.302611ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:03:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T13:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: d853ceb0-8348-4956-b7fb-5ba1004ad088
    resourceVersion: "27332"
    uid: 8a3faa84-a073-48ba-89ef-fb33967e68a1
  spec:
    sourcePod: network-check-source-56d84b9f44-xfl7b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T14:04:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.236012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 1.881683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:10:29Z"
    - latency: 1.347179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 1.853852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:09:29Z"
    - latency: 888.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 1.9024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:08:29Z"
    - latency: 1.067772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 1.859145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:07:29Z"
    - latency: 1.24167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T14:06:29Z"
    - latency: 1.858889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T14:06:29Z"
kind: List
metadata:
  resourceVersion: ""