apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "25956"
    uid: 481a8c72-d359-4baa-b794-dd3de4d6e19f
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:55:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.006µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:02:18Z"
    - latency: 761.451µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:01:18Z"
    - latency: 733.021µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 765.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 1.037974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 842.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 924.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 1.042537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:55:18Z"
    - latency: 1.168216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:54:18Z"
    - latency: 802.278µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:53:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "24737"
    uid: 5edd623c-35c9-4ddf-8a27-065b06d898b1
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:54:18Z"
      message: 'load-balancer-api-external: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.788037ms
      message: 'load-balancer-api-external: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 6.963853ms
      message: 'load-balancer-api-external: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 4.850844ms
      message: 'load-balancer-api-external: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 12.327236ms
      message: 'load-balancer-api-external: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 4.574605ms
      message: 'load-balancer-api-external: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 6.484414ms
      message: 'load-balancer-api-external: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 5.22068ms
      message: 'load-balancer-api-external: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 7.435238ms
      message: 'load-balancer-api-external: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 5.419831ms
      message: 'load-balancer-api-external: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 6.97026ms
      message: 'load-balancer-api-external: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "24738"
    uid: f44fa50d-060f-455d-9ec1-485c895cbf01
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:54:18Z"
      message: 'load-balancer-api-internal: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.797701ms
      message: 'load-balancer-api-internal: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 7.012671ms
      message: 'load-balancer-api-internal: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 4.816031ms
      message: 'load-balancer-api-internal: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 12.421633ms
      message: 'load-balancer-api-internal: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 4.906551ms
      message: 'load-balancer-api-internal: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 6.375502ms
      message: 'load-balancer-api-internal: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 5.18927ms
      message: 'load-balancer-api-internal: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 7.452435ms
      message: 'load-balancer-api-internal: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 6.183069ms
      message: 'load-balancer-api-internal: tcp connection to aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 6.994423ms
      message: 'load-balancer-api-internal: resolved host name aef3d97273f144a368d499648261919e-cd8cda5399421e75.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-131-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "25955"
    uid: 5818984d-20e7-44e0-ba1d-458aa62b3e3e
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:55:18Z"
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.041981ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:02:18Z"
    - latency: 2.176804ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:01:18Z"
    - latency: 2.085025ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 1.946349ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 2.153709ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 1.779202ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 1.938639ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 2.092229ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:55:18Z"
    - latency: 2.144829ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:54:18Z"
    - latency: 2.116092ms
      message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:53:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-137-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "25953"
    uid: 9285199c-7913-4e5e-8d0f-b0b36fa0ee5b
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:55:18Z"
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.265µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:02:18Z"
    - latency: 1.326479ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:01:18Z"
    - latency: 1.198375ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 767.169µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 714.528µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 1.243374ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 800.151µs
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 1.093523ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:55:18Z"
    - latency: 1.391912ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:54:18Z"
    - latency: 1.068652ms
      message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:53:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-ip-10-0-140-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "25954"
    uid: 498142f7-9fdb-4ac9-b03a-2dbebb24916e
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:55:18Z"
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.09254ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:02:18Z"
    - latency: 2.009781ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:01:18Z"
    - latency: 1.874162ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 1.889766ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 1.667011ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 1.752687ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 1.893508ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 1.671227ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:55:18Z"
    - latency: 2.096009ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:54:18Z"
    - latency: 1.82683ms
      message: 'network-check-target-ip-10-0-140-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:53:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T12:48:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-102.ec2.internal
      uid: a2b7811a-f540-47fb-be57-2e65648245ff
    resourceVersion: "24736"
    uid: 0090c625-6c15-4378-a8a7-93d9732e51d5
  spec:
    sourcePod: network-check-source-869dcfcdcd-m52mf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T12:54:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.189488ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 1.537227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T13:00:18Z"
    - latency: 897.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 1.678623ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:59:18Z"
    - latency: 872.75µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 1.640449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:58:18Z"
    - latency: 841.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 2.074688ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:57:18Z"
    - latency: 797.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T12:56:18Z"
    - latency: 1.654073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T12:56:18Z"
kind: List
metadata:
  resourceVersion: ""