apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "67881"
    uid: ebbfee4d-198a-4a72-b459-8583fb2aa95d
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:35:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.97µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 1.011319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 977.937µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 1.08905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 1.030933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:59:43Z"
    - latency: 941.159µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:58:43Z"
    - latency: 951.383µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:57:43Z"
    - latency: 1.024284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:56:43Z"
    - latency: 1.106142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:55:43Z"
    - latency: 1.254865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "68661"
    uid: eb3334f0-0bea-4c5f-b802-375a6672bc57
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:34:43Z"
      message: 'load-balancer-api-external: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.233324ms
      message: 'load-balancer-api-external: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:04:43Z"
    - latency: 8.21545ms
      message: 'load-balancer-api-external: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:04:43Z"
    - latency: 4.140298ms
      message: 'load-balancer-api-external: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 9.431639ms
      message: 'load-balancer-api-external: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 5.765734ms
      message: 'load-balancer-api-external: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 9.06969ms
      message: 'load-balancer-api-external: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 3.63608ms
      message: 'load-balancer-api-external: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 7.079923ms
      message: 'load-balancer-api-external: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 4.998777ms
      message: 'load-balancer-api-external: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 7.561412ms
      message: 'load-balancer-api-external: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:00:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "68660"
    uid: 51926851-2ce9-433c-9079-ee9e50e6c96a
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:34:43Z"
      message: 'load-balancer-api-internal: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.647117ms
      message: 'load-balancer-api-internal: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:04:43Z"
    - latency: 8.159351ms
      message: 'load-balancer-api-internal: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:04:43Z"
    - latency: 4.149581ms
      message: 'load-balancer-api-internal: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 9.383822ms
      message: 'load-balancer-api-internal: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 5.814605ms
      message: 'load-balancer-api-internal: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 9.004269ms
      message: 'load-balancer-api-internal: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 4.610669ms
      message: 'load-balancer-api-internal: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 6.936212ms
      message: 'load-balancer-api-internal: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 5.039251ms
      message: 'load-balancer-api-internal: tcp connection to a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 7.337008ms
      message: 'load-balancer-api-internal: resolved host name a3ffd80916a3b475ab81ef7e7779845f-a2237f12f088571d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:00:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-129-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "67880"
    uid: 6581a0df-e8b2-430b-b2e7-6637719ccd1d
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:35:43Z"
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.324854ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 2.341272ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 2.196251ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 2.475844ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 2.159363ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:59:43Z"
    - latency: 2.372034ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:58:43Z"
    - latency: 2.20709ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:57:43Z"
    - latency: 2.183491ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:56:43Z"
    - latency: 2.070687ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:55:43Z"
    - latency: 2.389698ms
      message: 'network-check-target-ip-10-0-129-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-137-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "67878"
    uid: d3e3fc37-5496-447c-85e3-426e5d76ab4a
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:35:43Z"
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 767.84µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 1.281391ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 874.332µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 1.357029ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 898.674µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:59:43Z"
    - latency: 1.285407ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:58:43Z"
    - latency: 1.035606ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:57:43Z"
    - latency: 1.030962ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:56:43Z"
    - latency: 953.857µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:55:43Z"
    - latency: 1.638163ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-141-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "67879"
    uid: a02c0c9a-a4d5-4f01-8f1a-2d9b48f484dd
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:35:43Z"
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.791633ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 1.769348ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 2.072432ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 1.973245ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 2.137449ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:59:43Z"
    - latency: 2.123013ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:58:43Z"
    - latency: 1.836339ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:57:43Z"
    - latency: 2.646812ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:56:43Z"
    - latency: 2.093417ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:55:43Z"
    - latency: 2.090779ms
      message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:28:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.ec2.internal
      uid: 0ffc8983-17da-4de4-a941-aac939ca2730
    resourceVersion: "68659"
    uid: 8f15fc60-32fe-4a7c-94f8-a0a9883a0e97
  spec:
    sourcePod: network-check-source-6f8b768455-m27xt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:34:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 873.901µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:04:43Z"
    - latency: 1.723868ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:04:43Z"
    - latency: 1.042097ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 1.982034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:03:43Z"
    - latency: 1.473058ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 1.648948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:02:43Z"
    - latency: 1.252303ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 1.751566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:01:43Z"
    - latency: 1.48515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T13:00:43Z"
    - latency: 2.16903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T13:00:43Z"
kind: List
metadata:
  resourceVersion: ""