apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "53948"
    uid: 322e0f8d-5b02-4ff6-81f7-7e10c5c82fb5
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:30:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 1.004352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 1.228918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 1.051707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:48:59Z"
    - latency: 1.168849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:47:59Z"
    - latency: 1.161362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:46:59Z"
    - latency: 1.043632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:45:59Z"
    - latency: 1.026987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:44:59Z"
    - latency: 1.291454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:43:59Z"
    - latency: 1.069336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:42:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "55609"
    uid: 13667e03-a7d6-43b4-9d5f-f486c4a43835
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:29:59Z"
      message: 'load-balancer-api-external: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.584899ms
      message: 'load-balancer-api-external: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:53:59Z"
    - latency: 8.349935ms
      message: 'load-balancer-api-external: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:53:59Z"
    - latency: 5.513651ms
      message: 'load-balancer-api-external: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:52:59Z"
    - latency: 13.402117ms
      message: 'load-balancer-api-external: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:52:59Z"
    - latency: 5.566039ms
      message: 'load-balancer-api-external: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 7.790241ms
      message: 'load-balancer-api-external: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 4.327407ms
      message: 'load-balancer-api-external: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 8.253306ms
      message: 'load-balancer-api-external: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 5.012402ms
      message: 'load-balancer-api-external: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 8.647356ms
      message: 'load-balancer-api-external: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:49:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "55610"
    uid: 75515721-5b54-4f3e-ad21-753b901bb53c
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:29:59Z"
      message: 'load-balancer-api-internal: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.666258ms
      message: 'load-balancer-api-internal: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:53:59Z"
    - latency: 8.247216ms
      message: 'load-balancer-api-internal: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:53:59Z"
    - latency: 5.562422ms
      message: 'load-balancer-api-internal: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:52:59Z"
    - latency: 13.349702ms
      message: 'load-balancer-api-internal: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:52:59Z"
    - latency: 4.293499ms
      message: 'load-balancer-api-internal: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 7.647851ms
      message: 'load-balancer-api-internal: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 5.273752ms
      message: 'load-balancer-api-internal: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 8.276073ms
      message: 'load-balancer-api-internal: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 4.248246ms
      message: 'load-balancer-api-internal: tcp connection to a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 8.723349ms
      message: 'load-balancer-api-internal: resolved host name a9bb686cd23c44cb597e9e279e8c8630-43ce508f07cf86c2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:49:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-network-check-target-ip-10-0-133-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "53944"
    uid: cb3249a0-0641-40d3-afce-a003c7ce050a
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:30:59Z"
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.361511ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 1.030163ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 1.05952ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 813.839µs
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:48:59Z"
    - latency: 1.564621ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:47:59Z"
    - latency: 995.491µs
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:46:59Z"
    - latency: 994.188µs
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:45:59Z"
    - latency: 1.46081ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:44:59Z"
    - latency: 1.646526ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:43:59Z"
    - latency: 1.043491ms
      message: 'network-check-target-ip-10-0-133-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:42:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-network-check-target-ip-10-0-139-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "53945"
    uid: 3bb5ca50-26c5-4d17-8663-b4f42d427404
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:30:59Z"
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.477487ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 2.709947ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 2.628975ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 2.435244ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:48:59Z"
    - latency: 2.974067ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:47:59Z"
    - latency: 2.251215ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:46:59Z"
    - latency: 2.20929ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:45:59Z"
    - latency: 2.402638ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:44:59Z"
    - latency: 3.092788ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:43:59Z"
    - latency: 2.634722ms
      message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:42:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-network-check-target-ip-10-0-140-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "53946"
    uid: e0410ca7-4ca0-46a6-bef2-8d9f210ef671
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:30:59Z"
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.497868ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 2.384245ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 2.400708ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 2.413958ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:48:59Z"
    - latency: 2.784272ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:47:59Z"
    - latency: 2.515802ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:46:59Z"
    - latency: 2.564861ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:45:59Z"
    - latency: 2.596669ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:44:59Z"
    - latency: 2.707177ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:43:59Z"
    - latency: 2.552381ms
      message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:42:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:23:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-152.ec2.internal
      uid: 8a186158-c9d6-4782-8fc2-ac020614ddc1
    resourceVersion: "55608"
    uid: cc3f4de9-6fb5-473f-aa61-5ac245dfea28
  spec:
    sourcePod: network-check-source-685456655f-ds22m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:29:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.163289ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:53:59Z"
    - latency: 1.846871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:53:59Z"
    - latency: 1.565463ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:52:59Z"
    - latency: 1.823911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:52:59Z"
    - latency: 899.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 2.250437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:51:59Z"
    - latency: 988.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 2.53841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:50:59Z"
    - latency: 992.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:49:59Z"
    - latency: 1.829577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:49:59Z"
kind: List
metadata:
  resourceVersion: ""