apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63339"
    uid: 163bd064-7a83-4eca-93c9-55f200fef0ef
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:46:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 929.314µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 1.293088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 1.156687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 1.180605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 1.22733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:16:54Z"
    - latency: 1.027407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:15:54Z"
    - latency: 1.059455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:14:54Z"
    - latency: 1.034564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:13:54Z"
    - latency: 1.233226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63340"
    uid: b3091cbb-0510-4988-9aaf-1d58b83ad912
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:45:54Z"
      message: 'load-balancer-api-external: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.972511ms
      message: 'load-balancer-api-external: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 8.585265ms
      message: 'load-balancer-api-external: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 4.99934ms
      message: 'load-balancer-api-external: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 8.623221ms
      message: 'load-balancer-api-external: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 4.450276ms
      message: 'load-balancer-api-external: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 8.231006ms
      message: 'load-balancer-api-external: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 5.185032ms
      message: 'load-balancer-api-external: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 20.486889ms
      message: 'load-balancer-api-external: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 4.92148ms
      message: 'load-balancer-api-external: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 8.519697ms
      message: 'load-balancer-api-external: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:17:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63341"
    uid: bb008fac-3b6b-4405-8f77-94d1f3594700
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:45:54Z"
      message: 'load-balancer-api-internal: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.114035ms
      message: 'load-balancer-api-internal: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 8.681256ms
      message: 'load-balancer-api-internal: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 4.661441ms
      message: 'load-balancer-api-internal: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 8.546067ms
      message: 'load-balancer-api-internal: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 3.887213ms
      message: 'load-balancer-api-internal: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 8.29523ms
      message: 'load-balancer-api-internal: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 4.600455ms
      message: 'load-balancer-api-internal: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 20.598403ms
      message: 'load-balancer-api-internal: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 3.39381ms
      message: 'load-balancer-api-internal: tcp connection to ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 8.617324ms
      message: 'load-balancer-api-internal: resolved host name ab5f2211bcfe6417c856415bf3d871b4-77c484264334a8f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:17:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-network-check-target-ip-10-0-134-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63335"
    uid: b504b267-0610-4e88-ba83-e6c07abe725b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:46:54Z"
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.445µs
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 1.044616ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 870.16µs
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 843.672µs
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 894.569µs
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 941.494µs
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:16:54Z"
    - latency: 1.356726ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:15:54Z"
    - latency: 1.091948ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:14:54Z"
    - latency: 1.086188ms
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:13:54Z"
    - latency: 851.412µs
      message: 'network-check-target-ip-10-0-134-236: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-network-check-target-ip-10-0-141-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63336"
    uid: 2644b05a-24cb-44ba-a66d-a156f0f27e70
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:46:54Z"
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382719ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 2.142754ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 2.534366ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 2.573318ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 2.515819ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 2.06282ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:16:54Z"
    - latency: 2.514993ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:15:54Z"
    - latency: 2.431342ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:14:54Z"
    - latency: 2.354943ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:13:54Z"
    - latency: 2.201278ms
      message: 'network-check-target-ip-10-0-141-203: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-network-check-target-ip-10-0-141-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63337"
    uid: eef14f56-8cd2-488b-a400-4f86ed507a61
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:46:54Z"
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.842323ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 1.906692ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 2.284222ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 2.309105ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 2.21426ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 1.818995ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:16:54Z"
    - latency: 1.99862ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:15:54Z"
    - latency: 2.056542ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:14:54Z"
    - latency: 2.368183ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:13:54Z"
    - latency: 2.238637ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:39:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-236-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-236.ec2.internal
      uid: 8877c7b0-36e5-428d-925c-70575c9dfefc
    resourceVersion: "63338"
    uid: 8d3b0a15-10a2-4651-b92c-9f36b882df51
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5ss74
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:45:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.445213ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 1.882392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:21:54Z"
    - latency: 916.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 1.797037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:20:54Z"
    - latency: 1.015144ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 2.032926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:19:54Z"
    - latency: 936.827µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 1.696645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:18:54Z"
    - latency: 920.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:17:54Z"
    - latency: 2.094973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:17:54Z"
kind: List
metadata:
  resourceVersion: ""