apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "23224"
    uid: 15927a9a-45fa-4421-a5f6-2a1e88a11657
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.473µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:16Z"
    - latency: 912.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:16Z"
    - latency: 1.288406ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:16Z"
    - latency: 1.37595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 905.933µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 843.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 1.151281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 750.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 941.648µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:16Z"
    - latency: 998.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "21802"
    uid: b9c8f713-aca9-4d30-a8ef-e93a324ae47a
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:16Z"
      message: 'load-balancer-api-external: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.307313ms
      message: 'load-balancer-api-external: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 8.837519ms
      message: 'load-balancer-api-external: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 7.602644ms
      message: 'load-balancer-api-external: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 8.266341ms
      message: 'load-balancer-api-external: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 6.864827ms
      message: 'load-balancer-api-external: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 8.544702ms
      message: 'load-balancer-api-external: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 7.512903ms
      message: 'load-balancer-api-external: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 8.296096ms
      message: 'load-balancer-api-external: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 5.491169ms
      message: 'load-balancer-api-external: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 8.570116ms
      message: 'load-balancer-api-external: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:58:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "21801"
    uid: 9bef0a20-a321-4f9f-96d4-6c241124de07
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:16Z"
      message: 'load-balancer-api-internal: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.343636ms
      message: 'load-balancer-api-internal: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 8.797845ms
      message: 'load-balancer-api-internal: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 5.018525ms
      message: 'load-balancer-api-internal: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 8.337083ms
      message: 'load-balancer-api-internal: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 4.332718ms
      message: 'load-balancer-api-internal: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 8.512899ms
      message: 'load-balancer-api-internal: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 7.233789ms
      message: 'load-balancer-api-internal: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 8.228435ms
      message: 'load-balancer-api-internal: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 5.519873ms
      message: 'load-balancer-api-internal: tcp connection to a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 8.649595ms
      message: 'load-balancer-api-internal: resolved host name a3ed11c4edaa848d8a61a9b6a9f22947-09c6f7a24a9b778b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:58:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-ip-10-0-134-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "23221"
    uid: 99bad2fd-2dbf-4d22-8fa2-f9854035d137
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:16Z"
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.397408ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:16Z"
    - latency: 2.267902ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:16Z"
    - latency: 2.26841ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:16Z"
    - latency: 2.830465ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 2.207002ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 2.307568ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 2.480116ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 1.837282ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 2.10015ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:16Z"
    - latency: 2.206127ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-ip-10-0-136-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "23223"
    uid: 8675227b-e698-417f-a3e7-f660f1c718b3
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:16Z"
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.146283ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:16Z"
    - latency: 2.261327ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:16Z"
    - latency: 2.447508ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:16Z"
    - latency: 2.162092ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 2.481762ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 2.196589ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 2.260109ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 2.166818ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 2.201884ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:16Z"
    - latency: 1.957298ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-ip-10-0-138-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "23222"
    uid: 54724d0f-db9b-4080-b231-f35b122b7d17
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:16Z"
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.07782ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:16Z"
    - latency: 934.356µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:16Z"
    - latency: 811.604µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:16Z"
    - latency: 920.689µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 1.340746ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 945.561µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 846.125µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 761.727µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 931.436µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:16Z"
    - latency: 1.174769ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: a2a2c0a1-dbbc-479b-9df2-152918929e6b
    resourceVersion: "21800"
    uid: 5552c6e1-daeb-439b-8467-56d6f28f5df0
  spec:
    sourcePod: network-check-source-7cbc45fddc-wt2kt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.841µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 2.016909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:02:16Z"
    - latency: 1.251745ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 1.591217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:01:16Z"
    - latency: 819.964µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 1.993155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:00:16Z"
    - latency: 861.694µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 1.848007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:59:16Z"
    - latency: 841.266µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:16Z"
    - latency: 1.753494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:58:16Z"
kind: List
metadata:
  resourceVersion: ""