apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "23666"
    uid: b3e09a0f-3695-4ec7-a793-78434bd618d9
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.116791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:35Z"
    - latency: 1.074999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:35Z"
    - latency: 1.068207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:35Z"
    - latency: 1.288338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 1.054115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 804.262µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 1.021175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 928.874µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 1.114758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:35Z"
    - latency: 1.112475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "22169"
    uid: 6db3fe0b-16be-40b0-b80f-ea6ac1e1d99b
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:35Z"
      message: 'load-balancer-api-external: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.845561ms
      message: 'load-balancer-api-external: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 8.284828ms
      message: 'load-balancer-api-external: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 4.113425ms
      message: 'load-balancer-api-external: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 9.158147ms
      message: 'load-balancer-api-external: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 6.333662ms
      message: 'load-balancer-api-external: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 9.380657ms
      message: 'load-balancer-api-external: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 6.298752ms
      message: 'load-balancer-api-external: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 8.407929ms
      message: 'load-balancer-api-external: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 4.443985ms
      message: 'load-balancer-api-external: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 8.174867ms
      message: 'load-balancer-api-external: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:04:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "22170"
    uid: a300169d-848b-4784-a12a-8c8e0c7f30ca
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:35Z"
      message: 'load-balancer-api-internal: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.83275ms
      message: 'load-balancer-api-internal: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 8.199876ms
      message: 'load-balancer-api-internal: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 4.072118ms
      message: 'load-balancer-api-internal: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 9.21667ms
      message: 'load-balancer-api-internal: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 6.322746ms
      message: 'load-balancer-api-internal: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 9.33045ms
      message: 'load-balancer-api-internal: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 6.303478ms
      message: 'load-balancer-api-internal: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 8.507127ms
      message: 'load-balancer-api-internal: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 4.503268ms
      message: 'load-balancer-api-internal: tcp connection to a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 8.087411ms
      message: 'load-balancer-api-internal: resolved host name a9bfa2157927a4d16bc9c10bf767b1ce-0a01d19338bbd9e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:04:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-128-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "23664"
    uid: fd8a8f83-93c5-4aca-8a9a-06d3e8080b42
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:35Z"
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297841ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:35Z"
    - latency: 2.212945ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:35Z"
    - latency: 2.11988ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:35Z"
    - latency: 2.196734ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 2.189753ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 2.538324ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 2.391572ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 2.209584ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 2.816899ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:35Z"
    - latency: 2.21361ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-140-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "23663"
    uid: d4928f98-64cd-4ffa-bdb8-f2dedebf307d
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:35Z"
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.49378ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:35Z"
    - latency: 809.299µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:35Z"
    - latency: 772.966µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:35Z"
    - latency: 1.067184ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 880.293µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 779.918µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 920.113µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 813.722µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 780.42µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:35Z"
    - latency: 968.853µs
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-143-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "23665"
    uid: 14bd8a8b-7518-4312-a148-c639c9a612e1
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:35Z"
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.244794ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:35Z"
    - latency: 1.810786ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:35Z"
    - latency: 1.905744ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:35Z"
    - latency: 2.013941ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 2.150351ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 1.993879ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 1.984506ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 2.033464ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 2.297398ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:35Z"
    - latency: 1.876395ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-230.ec2.internal
      uid: d99ef770-a585-491b-8900-52d60ec2e1e6
    resourceVersion: "22168"
    uid: dc6a5a86-1f37-4e71-aed4-f4395cb231bd
  spec:
    sourcePod: network-check-source-6f8b768455-6lmhf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041777ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 1.595402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:08:35Z"
    - latency: 865.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 1.802545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:07:35Z"
    - latency: 922.137µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 1.745078ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:06:35Z"
    - latency: 1.461622ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 1.675718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:05:35Z"
    - latency: 1.283168ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:35Z"
    - latency: 1.880271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:04:35Z"
kind: List
metadata:
  resourceVersion: ""