apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "54777"
    uid: 6226b2ad-1894-43ab-8f12-0eb4943ca34d
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:19:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 775.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 1.197627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 1.088539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 1.099199ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:43:26Z"
    - latency: 989.692µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:42:26Z"
    - latency: 825.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:26Z"
    - latency: 940.634µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:26Z"
    - latency: 1.112344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:26Z"
    - latency: 964.324µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "55890"
    uid: 01bf1f4e-c47d-4faf-8905-6e57525f88c6
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:18:26Z"
      message: 'load-balancer-api-external: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.177533ms
      message: 'load-balancer-api-external: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:48:26Z"
    - latency: 7.354427ms
      message: 'load-balancer-api-external: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:48:26Z"
    - latency: 5.452515ms
      message: 'load-balancer-api-external: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 8.553013ms
      message: 'load-balancer-api-external: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 5.292838ms
      message: 'load-balancer-api-external: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 7.483322ms
      message: 'load-balancer-api-external: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 3.927105ms
      message: 'load-balancer-api-external: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 8.610635ms
      message: 'load-balancer-api-external: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 5.686483ms
      message: 'load-balancer-api-external: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 8.860622ms
      message: 'load-balancer-api-external: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:44:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "55889"
    uid: 93574667-ab80-43af-945c-25b67d5f6eed
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:18:26Z"
      message: 'load-balancer-api-internal: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.045631ms
      message: 'load-balancer-api-internal: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:48:26Z"
    - latency: 7.429832ms
      message: 'load-balancer-api-internal: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:48:26Z"
    - latency: 5.427744ms
      message: 'load-balancer-api-internal: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 8.602325ms
      message: 'load-balancer-api-internal: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 6.453156ms
      message: 'load-balancer-api-internal: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 7.575987ms
      message: 'load-balancer-api-internal: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 4.163455ms
      message: 'load-balancer-api-internal: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 8.643198ms
      message: 'load-balancer-api-internal: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 5.778489ms
      message: 'load-balancer-api-internal: tcp connection to a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 8.776797ms
      message: 'load-balancer-api-internal: resolved host name a61798919f2c34101bcbee122b02a767-e9c389d5ecfea3cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:44:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-network-check-target-ip-10-0-132-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "54775"
    uid: df09239c-5792-4221-b99e-49a954627ae5
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:19:26Z"
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.570614ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 2.032556ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 2.35867ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 2.074784ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 2.280806ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:43:26Z"
    - latency: 2.495336ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:42:26Z"
    - latency: 3.004906ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:26Z"
    - latency: 2.565317ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:26Z"
    - latency: 2.137731ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:26Z"
    - latency: 2.675501ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-network-check-target-ip-10-0-141-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "54776"
    uid: cb4c5e32-4ca3-4633-99e1-9a66914090f5
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:19:26Z"
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.253509ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 2.112619ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 2.269437ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 2.191057ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 2.795938ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:43:26Z"
    - latency: 2.341187ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:42:26Z"
    - latency: 2.410998ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:26Z"
    - latency: 2.096863ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:26Z"
    - latency: 1.791192ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:26Z"
    - latency: 1.908953ms
      message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-network-check-target-ip-10-0-142-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "54774"
    uid: 2fee6160-354d-4861-afba-24256eea8a11
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:19:26Z"
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.826µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 911.389µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 826.657µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 921.959µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 1.406161ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:43:26Z"
    - latency: 878.56µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:42:26Z"
    - latency: 1.208481ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:26Z"
    - latency: 971.738µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:26Z"
    - latency: 892.249µs
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:26Z"
    - latency: 1.005303ms
      message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:12:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-232.ec2.internal
      uid: 4e2387cb-cf7a-4ce9-b8fd-d0bae24fd083
    resourceVersion: "55888"
    uid: ac175bc9-2881-4c34-9f18-da5f8b7a5281
  spec:
    sourcePod: network-check-source-989f8b8dc-mlj2v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:18:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:48:26Z"
    - latency: 1.849362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:48:26Z"
    - latency: 816.983µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 1.846047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:47:26Z"
    - latency: 816.19µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 1.701251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:46:26Z"
    - latency: 1.011692ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 1.931507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:45:26Z"
    - latency: 891.244µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:44:26Z"
    - latency: 2.029888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:44:26Z"
kind: List
metadata:
  resourceVersion: ""