apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "19273"
    uid: 306c56ff-f9ed-4b2a-a4e4-365f54beff71
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:48:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 827.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 857.604µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:00:52Z"
    - latency: 1.003351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:59:52Z"
    - latency: 1.092605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:58:52Z"
    - latency: 1.039201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:57:52Z"
    - latency: 988.238µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:56:52Z"
    - latency: 904.21µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:55:52Z"
    - latency: 1.010879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:54:52Z"
    - latency: 1.013288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "20544"
    uid: 9e6df34d-32b0-4681-a128-e63a190bdbeb
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:47:52Z"
      message: 'load-balancer-api-external: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.520264ms
      message: 'load-balancer-api-external: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:05:52Z"
    - latency: 7.548495ms
      message: 'load-balancer-api-external: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:05:52Z"
    - latency: 4.87543ms
      message: 'load-balancer-api-external: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:04:52Z"
    - latency: 16.910828ms
      message: 'load-balancer-api-external: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:04:52Z"
    - latency: 5.572763ms
      message: 'load-balancer-api-external: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:03:52Z"
    - latency: 8.100905ms
      message: 'load-balancer-api-external: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:03:52Z"
    - latency: 4.968827ms
      message: 'load-balancer-api-external: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 8.662756ms
      message: 'load-balancer-api-external: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 5.057292ms
      message: 'load-balancer-api-external: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 8.674733ms
      message: 'load-balancer-api-external: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:01:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "20543"
    uid: 90e05913-ab30-406f-a56e-3b9de12ba907
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:47:52Z"
      message: 'load-balancer-api-internal: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.454424ms
      message: 'load-balancer-api-internal: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:05:52Z"
    - latency: 7.612346ms
      message: 'load-balancer-api-internal: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:05:52Z"
    - latency: 4.946991ms
      message: 'load-balancer-api-internal: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:04:52Z"
    - latency: 17.01026ms
      message: 'load-balancer-api-internal: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:04:52Z"
    - latency: 4.717933ms
      message: 'load-balancer-api-internal: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:03:52Z"
    - latency: 8.192951ms
      message: 'load-balancer-api-internal: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:03:52Z"
    - latency: 4.962977ms
      message: 'load-balancer-api-internal: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 8.789962ms
      message: 'load-balancer-api-internal: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 4.599184ms
      message: 'load-balancer-api-internal: tcp connection to a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 8.727448ms
      message: 'load-balancer-api-internal: resolved host name a7dab4d7993eb4a50b649ccc9a391796-d3dbf61fb6580039.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:01:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-network-check-target-ip-10-0-128-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "19272"
    uid: bf334672-7461-4093-b18e-1253f3e598f0
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:48:52Z"
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.911367ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 2.149699ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 1.918329ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:00:52Z"
    - latency: 2.042307ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:59:52Z"
    - latency: 1.711821ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:58:52Z"
    - latency: 5.957574ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:57:52Z"
    - latency: 1.680226ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:56:52Z"
    - latency: 1.69552ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:55:52Z"
    - latency: 1.935543ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:54:52Z"
    - latency: 1.737287ms
      message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-network-check-target-ip-10-0-133-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "19271"
    uid: ae219977-5367-416d-aa75-4be6f1f65fc0
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:48:52Z"
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.897269ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 1.763696ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 1.891933ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:00:52Z"
    - latency: 1.563805ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:59:52Z"
    - latency: 1.863839ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:58:52Z"
    - latency: 1.788767ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:57:52Z"
    - latency: 1.562065ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:56:52Z"
    - latency: 1.898224ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:55:52Z"
    - latency: 1.886231ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:54:52Z"
    - latency: 1.784826ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-network-check-target-ip-10-0-137-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "19270"
    uid: c8205328-870d-492f-8fa5-433e8fa1cd73
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:48:52Z"
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.184384ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 910.952µs
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 1.1521ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:00:52Z"
    - latency: 1.272402ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:59:52Z"
    - latency: 1.077738ms
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:58:52Z"
    - latency: 784.175µs
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:57:52Z"
    - latency: 778.974µs
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:56:52Z"
    - latency: 894.72µs
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:55:52Z"
    - latency: 977.372µs
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:54:52Z"
    - latency: 959.697µs
      message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T08:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T08:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-144.ec2.internal
      uid: b03b034f-ccb9-4daa-8a07-c00336bc377e
    resourceVersion: "20542"
    uid: 6f70e9c6-3e3d-402b-9693-9fba925f6cef
  spec:
    sourcePod: network-check-source-685456655f-p45dk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T08:47:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.389µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:05:52Z"
    - latency: 1.910179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:05:52Z"
    - latency: 1.022632ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:04:52Z"
    - latency: 2.276768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:04:52Z"
    - latency: 947.856µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:03:52Z"
    - latency: 1.896422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:03:52Z"
    - latency: 835.054µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 1.869427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:02:52Z"
    - latency: 844.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T09:01:52Z"
    - latency: 2.247534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T09:01:52Z"
kind: List
metadata:
  resourceVersion: ""