apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "26420"
    uid: 4c36c1cc-8438-434b-90f9-ba18a277a666
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:36:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:41Z"
    - latency: 801.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:41Z"
    - latency: 1.211189ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 820.049µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 1.039028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 937.054µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 1.625212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 898.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:41Z"
    - latency: 1.097266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:41Z"
    - latency: 1.179493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "25214"
    uid: c719ffdd-d0fd-4165-8064-202b4d7e6613
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:35:41Z"
      message: 'load-balancer-api-external: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.636496ms
      message: 'load-balancer-api-external: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 15.410969ms
      message: 'load-balancer-api-external: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 5.354377ms
      message: 'load-balancer-api-external: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 8.607483ms
      message: 'load-balancer-api-external: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 5.099784ms
      message: 'load-balancer-api-external: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 8.368705ms
      message: 'load-balancer-api-external: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 5.10334ms
      message: 'load-balancer-api-external: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 8.888413ms
      message: 'load-balancer-api-external: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 5.142945ms
      message: 'load-balancer-api-external: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 8.621792ms
      message: 'load-balancer-api-external: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:37:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "25213"
    uid: 73bc2141-e3a1-45f4-b69a-343f07f1e412
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:35:41Z"
      message: 'load-balancer-api-internal: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.264946ms
      message: 'load-balancer-api-internal: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 15.47073ms
      message: 'load-balancer-api-internal: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 5.120217ms
      message: 'load-balancer-api-internal: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 8.575945ms
      message: 'load-balancer-api-internal: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 5.106281ms
      message: 'load-balancer-api-internal: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 8.42043ms
      message: 'load-balancer-api-internal: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 5.124872ms
      message: 'load-balancer-api-internal: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 8.935464ms
      message: 'load-balancer-api-internal: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 5.979364ms
      message: 'load-balancer-api-internal: tcp connection to aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 8.590497ms
      message: 'load-balancer-api-internal: resolved host name aaa04ab8999c14c8a84328eae36cffcb-7f5204e63797e66b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:37:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-network-check-target-ip-10-0-137-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "26418"
    uid: e2f9e41d-f07a-4af8-bfa9-fec59aa5a2ab
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:36:41Z"
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.726772ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:41Z"
    - latency: 1.716536ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:41Z"
    - latency: 1.791828ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 1.722404ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 1.806316ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 1.821447ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 1.760904ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 1.495059ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:41Z"
    - latency: 1.721333ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:41Z"
    - latency: 1.682184ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-network-check-target-ip-10-0-140-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "26419"
    uid: ff65e686-86ad-428f-be05-51fea33e6524
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:36:41Z"
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204537ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:41Z"
    - latency: 2.115038ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:41Z"
    - latency: 2.40484ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 2.289612ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 1.703767ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 1.969972ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 2.062428ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 2.260896ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:41Z"
    - latency: 2.315109ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:41Z"
    - latency: 1.810292ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-network-check-target-ip-10-0-141-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "26417"
    uid: acb083df-1635-4855-9eb2-dcdad4219ed2
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:36:41Z"
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.886µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:43:41Z"
    - latency: 1.232483ms
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:42:41Z"
    - latency: 865.035µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 777.303µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 763.903µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 850.421µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 782.892µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 2.150171ms
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:36:41Z"
    - latency: 805.385µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:35:41Z"
    - latency: 809.296µs
      message: 'network-check-target-ip-10-0-141-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:29:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-137.ec2.internal
      uid: 4a37b465-d902-4cb4-affc-42330def07d0
    resourceVersion: "25212"
    uid: 71afd101-6737-432c-8c4c-3def72748e42
  spec:
    sourcePod: network-check-source-989f8b8dc-nt6tl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:35:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.852µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 2.339276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:41:41Z"
    - latency: 818.146µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 1.697344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:40:41Z"
    - latency: 906.091µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 1.797967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:39:41Z"
    - latency: 880.783µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 1.809591ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:38:41Z"
    - latency: 1.015809ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:37:41Z"
    - latency: 1.809061ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:37:41Z"
kind: List
metadata:
  resourceVersion: ""