apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64084"
    uid: 231d1bea-1141-461d-bf83-17ee4f41d57a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:30:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 1.269591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 1.175655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 861.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 965.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 948.119µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:00:15Z"
    - latency: 876.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:59:15Z"
    - latency: 882.576µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:58:15Z"
    - latency: 1.252624ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:57:15Z"
    - latency: 1.28599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64085"
    uid: df2a627b-8286-417f-8796-76f35580cdd3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:29:15Z"
      message: 'load-balancer-api-external: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.452886ms
      message: 'load-balancer-api-external: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 6.537228ms
      message: 'load-balancer-api-external: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 3.719702ms
      message: 'load-balancer-api-external: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 6.726781ms
      message: 'load-balancer-api-external: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 3.875668ms
      message: 'load-balancer-api-external: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 7.187865ms
      message: 'load-balancer-api-external: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 4.619549ms
      message: 'load-balancer-api-external: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 7.564712ms
      message: 'load-balancer-api-external: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 3.829816ms
      message: 'load-balancer-api-external: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 8.166025ms
      message: 'load-balancer-api-external: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:01:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64086"
    uid: 86efc42d-9dfb-4758-b7d5-9d7c190c3815
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:29:15Z"
      message: 'load-balancer-api-internal: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.754352ms
      message: 'load-balancer-api-internal: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 6.443463ms
      message: 'load-balancer-api-internal: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 3.659421ms
      message: 'load-balancer-api-internal: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 6.818705ms
      message: 'load-balancer-api-internal: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 3.968041ms
      message: 'load-balancer-api-internal: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 7.135366ms
      message: 'load-balancer-api-internal: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 4.60641ms
      message: 'load-balancer-api-internal: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 7.507995ms
      message: 'load-balancer-api-internal: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 3.575762ms
      message: 'load-balancer-api-internal: tcp connection to a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 8.137249ms
      message: 'load-balancer-api-internal: resolved host name a0b544444c2da4f3d8f0a568e56f330c-6fc5c0132d661727.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:01:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-network-check-target-ip-10-0-139-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64082"
    uid: 03cdabf6-b316-42a7-9fa4-6fdfa569c2b5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:30:15Z"
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.789315ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 2.367356ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 2.730014ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 2.223956ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 2.561416ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 2.700312ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:00:15Z"
    - latency: 2.352423ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:59:15Z"
    - latency: 2.520417ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:58:15Z"
    - latency: 2.556474ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:57:15Z"
    - latency: 2.208485ms
      message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-network-check-target-ip-10-0-140-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64081"
    uid: 3ac4af06-ea6b-4c04-94f9-8ea1bb7f3f49
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:30:15Z"
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.553621ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 2.498122ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 2.76841ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 2.447421ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 2.548273ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 2.366042ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:00:15Z"
    - latency: 2.266058ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:59:15Z"
    - latency: 2.589729ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:58:15Z"
    - latency: 2.562172ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:57:15Z"
    - latency: 2.089308ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-network-check-target-ip-10-0-141-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64080"
    uid: 16e594db-3c63-4d48-92aa-4f2556d40b56
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:30:15Z"
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.558308ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 980.779µs
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 1.579297ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 982.551µs
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 1.017732ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 1.029433ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:00:15Z"
    - latency: 1.312398ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:59:15Z"
    - latency: 1.270597ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:58:15Z"
    - latency: 1.338047ms
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:57:15Z"
    - latency: 864.683µs
      message: 'network-check-target-ip-10-0-141-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T00:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T00:23:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-120.ec2.internal
      uid: 4e76783d-01dd-42f3-8e4a-98ca510811c5
    resourceVersion: "64083"
    uid: 8b2a94c2-d13f-439f-b8b5-5fc1300bc180
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zx22r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T00:29:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003509ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 2.203803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:05:15Z"
    - latency: 1.049913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 1.731198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:04:15Z"
    - latency: 1.164261ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 2.235601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:03:15Z"
    - latency: 937.036µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 1.891486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:02:15Z"
    - latency: 1.164351ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:01:15Z"
    - latency: 1.589592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T01:01:15Z"
kind: List
metadata:
  resourceVersion: ""