apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63147"
    uid: a995d379-010e-413b-977b-1c1d86231dc4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:46:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 891.24µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 920.135µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 950.239µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 1.363785ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 1.506677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:16:37Z"
    - latency: 1.109255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:15:37Z"
    - latency: 1.066245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:14:37Z"
    - latency: 1.145093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:13:37Z"
    - latency: 1.640159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:12:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63150"
    uid: ba0cce5e-a7e3-4168-8492-8c8234435a15
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:45:37Z"
      message: 'load-balancer-api-external: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.0614ms
      message: 'load-balancer-api-external: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 7.732947ms
      message: 'load-balancer-api-external: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 3.886758ms
      message: 'load-balancer-api-external: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 7.139031ms
      message: 'load-balancer-api-external: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 5.466748ms
      message: 'load-balancer-api-external: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 10.046025ms
      message: 'load-balancer-api-external: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 4.163334ms
      message: 'load-balancer-api-external: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 7.997988ms
      message: 'load-balancer-api-external: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 5.285793ms
      message: 'load-balancer-api-external: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 7.450884ms
      message: 'load-balancer-api-external: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:17:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63149"
    uid: 5dbfb4a8-d65d-4074-ba23-dfa7220c1764
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:45:37Z"
      message: 'load-balancer-api-internal: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.062835ms
      message: 'load-balancer-api-internal: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 7.675166ms
      message: 'load-balancer-api-internal: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 4.509999ms
      message: 'load-balancer-api-internal: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 7.166078ms
      message: 'load-balancer-api-internal: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 5.500828ms
      message: 'load-balancer-api-internal: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 10.120471ms
      message: 'load-balancer-api-internal: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 4.144993ms
      message: 'load-balancer-api-internal: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 8.048072ms
      message: 'load-balancer-api-internal: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 5.350902ms
      message: 'load-balancer-api-internal: tcp connection to a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 7.433537ms
      message: 'load-balancer-api-internal: resolved host name a7f14115ddeb045caaf6dd8bcdf685f1-cc59c9831daaa89f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:17:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-network-check-target-ip-10-0-129-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63144"
    uid: e80e9f39-f352-484b-a00e-07fa8e5083b0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:46:37Z"
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.30612ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 1.944875ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 2.578212ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 1.994061ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 2.346161ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 2.437726ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:16:37Z"
    - latency: 2.19676ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:15:37Z"
    - latency: 2.09069ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:14:37Z"
    - latency: 2.901252ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:13:37Z"
    - latency: 2.561017ms
      message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:12:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-network-check-target-ip-10-0-138-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63145"
    uid: 01f3a531-ddbb-455a-94aa-54d27c2b0d63
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:46:37Z"
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.099271ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 2.140213ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 2.274064ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 1.939724ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 2.226484ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 2.147904ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:16:37Z"
    - latency: 2.361569ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:15:37Z"
    - latency: 2.189168ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:14:37Z"
    - latency: 2.61471ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:13:37Z"
    - latency: 2.369535ms
      message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:12:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-network-check-target-ip-10-0-139-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63143"
    uid: 6811077e-a80e-4158-8501-115b33adf372
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:46:37Z"
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.379154ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 1.607449ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 1.165668ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 1.191458ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 1.562049ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 1.096543ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:16:37Z"
    - latency: 1.030775ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:15:37Z"
    - latency: 1.021901ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:14:37Z"
    - latency: 1.643552ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:13:37Z"
    - latency: 1.621934ms
      message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:12:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:39:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-183.ec2.internal
      uid: b9645b50-a717-4d2f-b499-67820348523e
    resourceVersion: "63146"
    uid: bc0de08c-eb97-4d1c-a7f9-d7ed78695ea6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dprcn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:45:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.376493ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 1.740071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:21:37Z"
    - latency: 1.328994ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 1.652247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:20:37Z"
    - latency: 1.040035ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 1.866935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:19:37Z"
    - latency: 926.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 2.434792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:18:37Z"
    - latency: 1.301312ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:17:37Z"
    - latency: 2.215318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:17:37Z"
kind: List
metadata:
  resourceVersion: ""