apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "148714"
    uid: 909f3284-baf8-4280-830a-55579117e79e
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:55:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.882574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 1.242731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 1.252438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:49:52Z"
    - latency: 883.615µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:48:52Z"
    - latency: 1.644958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:47:52Z"
    - latency: 1.436845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:46:52Z"
    - latency: 920.16µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:45:52Z"
    - latency: 2.200315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:44:52Z"
    - latency: 983.407µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:43:52Z"
    - latency: 1.086212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "152650"
    uid: bb9facc4-6b44-464c-9740-aeb6735d44e5
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:54:52Z"
      message: 'load-balancer-api-external: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.144685ms
      message: 'load-balancer-api-external: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:54:52Z"
    - latency: 8.988591ms
      message: 'load-balancer-api-external: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:54:52Z"
    - latency: 17.104393ms
      message: 'load-balancer-api-external: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:53:52Z"
    - latency: 12.609082ms
      message: 'load-balancer-api-external: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:53:52Z"
    - latency: 18.116664ms
      message: 'load-balancer-api-external: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:52:52Z"
    - latency: 7.05895ms
      message: 'load-balancer-api-external: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:52:52Z"
    - latency: 17.818444ms
      message: 'load-balancer-api-external: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 9.361454ms
      message: 'load-balancer-api-external: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 17.203125ms
      message: 'load-balancer-api-external: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 7.280121ms
      message: 'load-balancer-api-external: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:50:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "152649"
    uid: 6d6ce096-321a-4c82-8099-b2fb3d8b0feb
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:54:52Z"
      message: 'load-balancer-api-internal: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.965515ms
      message: 'load-balancer-api-internal: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:54:52Z"
    - latency: 9.053063ms
      message: 'load-balancer-api-internal: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:54:52Z"
    - latency: 18.879873ms
      message: 'load-balancer-api-internal: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:53:52Z"
    - latency: 12.712885ms
      message: 'load-balancer-api-internal: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:53:52Z"
    - latency: 18.382082ms
      message: 'load-balancer-api-internal: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:52:52Z"
    - latency: 7.109679ms
      message: 'load-balancer-api-internal: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:52:52Z"
    - latency: 18.092479ms
      message: 'load-balancer-api-internal: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 9.446366ms
      message: 'load-balancer-api-internal: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 17.232564ms
      message: 'load-balancer-api-internal: tcp connection to a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 7.275066ms
      message: 'load-balancer-api-internal: resolved host name a32dc76ee693f490c84982b3eca5db0e-dd9a7d0b5f511b2b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:50:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-ip-10-0-138-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "148711"
    uid: 4648163a-5b4f-4417-9eea-0655010a0d38
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:55:52Z"
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015809ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 949.26µs
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 1.180243ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:49:52Z"
    - latency: 1.25758ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:48:52Z"
    - latency: 939.45µs
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:47:52Z"
    - latency: 1.057748ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:46:52Z"
    - latency: 876.689µs
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:45:52Z"
    - latency: 1.644587ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:44:52Z"
    - latency: 1.66174ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:43:52Z"
    - latency: 1.12271ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-ip-10-0-139-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "148712"
    uid: ce47010d-2b01-49cf-abe6-f8fcd95a4f92
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:55:52Z"
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.185782ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 2.251677ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 2.437658ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:49:52Z"
    - latency: 2.222725ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:48:52Z"
    - latency: 2.073827ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:47:52Z"
    - latency: 1.93128ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:46:52Z"
    - latency: 2.054735ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:45:52Z"
    - latency: 2.982594ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:44:52Z"
    - latency: 2.29983ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:43:52Z"
    - latency: 2.004897ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-ip-10-0-142-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "148713"
    uid: 46f0fc92-48c3-4fa8-b3c8-e73b64f792ab
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:55:52Z"
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.443518ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 2.164991ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 2.239953ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:49:52Z"
    - latency: 2.486181ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:48:52Z"
    - latency: 2.321301ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:47:52Z"
    - latency: 2.499694ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:46:52Z"
    - latency: 2.320697ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:45:52Z"
    - latency: 3.122393ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:44:52Z"
    - latency: 2.539036ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:43:52Z"
    - latency: 2.536324ms
      message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:42:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:48:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 3e6b4d9e-5452-4567-a198-20738005daa1
    resourceVersion: "152648"
    uid: 223ee309-eeb8-4f07-ab48-71431a2e61d5
  spec:
    sourcePod: network-check-source-6f78d59f99-k5zrz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:54:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:54:52Z"
    - latency: 3.459127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:54:52Z"
    - latency: 1.245177ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:53:52Z"
    - latency: 2.5053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:53:52Z"
    - latency: 1.077765ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:52:52Z"
    - latency: 2.084495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:52:52Z"
    - latency: 1.145045ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 2.294627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:51:52Z"
    - latency: 1.030861ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:50:52Z"
    - latency: 1.873579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:50:52Z"
kind: List
metadata:
  resourceVersion: ""