apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "65805"
    uid: 7bec6cc7-4da2-4ee4-9371-d5c3a1989563
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:09:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 954.992µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 956.538µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 1.00544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 1.08375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:12Z"
    - latency: 831.767µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:32:12Z"
    - latency: 975.22µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:31:12Z"
    - latency: 1.241073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:30:12Z"
    - latency: 1.210809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:12Z"
    - latency: 1.167939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "66634"
    uid: f10360d1-874b-4cf2-99ef-9b3dedbe2963
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:08:12Z"
      message: 'load-balancer-api-external: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.247438ms
      message: 'load-balancer-api-external: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:12Z"
    - latency: 7.804214ms
      message: 'load-balancer-api-external: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:12Z"
    - latency: 4.403629ms
      message: 'load-balancer-api-external: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 7.397522ms
      message: 'load-balancer-api-external: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 6.159611ms
      message: 'load-balancer-api-external: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 7.840658ms
      message: 'load-balancer-api-external: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 3.874948ms
      message: 'load-balancer-api-external: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 9.941746ms
      message: 'load-balancer-api-external: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 3.799469ms
      message: 'load-balancer-api-external: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 8.00003ms
      message: 'load-balancer-api-external: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:34:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "66633"
    uid: 2114aed6-9821-4fe4-8dc0-d118e4f491b2
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:08:12Z"
      message: 'load-balancer-api-internal: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.251204ms
      message: 'load-balancer-api-internal: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:12Z"
    - latency: 7.811804ms
      message: 'load-balancer-api-internal: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:12Z"
    - latency: 5.584258ms
      message: 'load-balancer-api-internal: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 7.370489ms
      message: 'load-balancer-api-internal: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 6.203774ms
      message: 'load-balancer-api-internal: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 7.792047ms
      message: 'load-balancer-api-internal: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 4.208479ms
      message: 'load-balancer-api-internal: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 9.913812ms
      message: 'load-balancer-api-internal: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 3.881959ms
      message: 'load-balancer-api-internal: tcp connection to a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 7.883545ms
      message: 'load-balancer-api-internal: resolved host name a0d63381f02634620810c71e613eaeef-bf46d03a8d996796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:34:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-network-check-target-ip-10-0-130-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "65803"
    uid: 869ecccf-577d-4f1b-983f-fb0073a8a967
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:09:12Z"
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.992138ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 2.317688ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 2.310675ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 2.860489ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 2.535852ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:12Z"
    - latency: 2.350547ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:32:12Z"
    - latency: 2.450177ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:31:12Z"
    - latency: 2.430656ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:30:12Z"
    - latency: 2.218064ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:12Z"
    - latency: 2.540325ms
      message: 'network-check-target-ip-10-0-130-248: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-network-check-target-ip-10-0-132-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "65802"
    uid: 04b5bfe1-70b4-4f97-b22a-5ea8befedb3c
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:09:12Z"
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 783.863µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 838.933µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 876.596µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 871.056µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 858.905µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:12Z"
    - latency: 886.945µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:32:12Z"
    - latency: 1.406294ms
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:31:12Z"
    - latency: 1.47802ms
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:30:12Z"
    - latency: 844.647µs
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:12Z"
    - latency: 1.370392ms
      message: 'network-check-target-ip-10-0-132-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-network-check-target-ip-10-0-140-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "65804"
    uid: b6b5c769-382e-443f-9b0d-cf44c2b5f0dc
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:09:12Z"
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.377815ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 2.666208ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 2.754497ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 2.533763ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 2.600336ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:12Z"
    - latency: 2.573589ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:32:12Z"
    - latency: 2.789755ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:31:12Z"
    - latency: 2.683017ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:30:12Z"
    - latency: 2.451049ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:12Z"
    - latency: 2.66737ms
      message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:02:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-172.ec2.internal
      uid: 1cba04d1-0d86-4ea2-ac86-0a7e03c1eda5
    resourceVersion: "66632"
    uid: 451f650f-f31e-494a-ad66-7f49ee1aa838
  spec:
    sourcePod: network-check-source-7cbc45fddc-hrwj8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:08:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:12Z"
    - latency: 1.764138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:12Z"
    - latency: 1.249121ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 2.009113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:12Z"
    - latency: 858.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 1.648435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:36:12Z"
    - latency: 761.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 1.647711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:35:12Z"
    - latency: 990.261µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:12Z"
    - latency: 1.820284ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:34:12Z"
kind: List
metadata:
  resourceVersion: ""