apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "67673"
    uid: af6ce95c-719b-4127-a8b6-3dc915f6ba73
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:57:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.145677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 1.245294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 1.133372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 1.228691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 1.168418ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:21:41Z"
    - latency: 1.380256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:20:41Z"
    - latency: 1.09021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:19:41Z"
    - latency: 1.49967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:18:41Z"
    - latency: 1.485504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:17:41Z"
    - latency: 979.5µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:16:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "68308"
    uid: ff4c3db3-bc7e-44d4-9f3e-006951ce9b0f
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:56:41Z"
      message: 'load-balancer-api-external: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.929567ms
      message: 'load-balancer-api-external: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:26:41Z"
    - latency: 7.408729ms
      message: 'load-balancer-api-external: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:26:41Z"
    - latency: 4.385977ms
      message: 'load-balancer-api-external: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 8.873292ms
      message: 'load-balancer-api-external: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 4.716195ms
      message: 'load-balancer-api-external: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 9.277208ms
      message: 'load-balancer-api-external: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 4.0674ms
      message: 'load-balancer-api-external: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 12.051407ms
      message: 'load-balancer-api-external: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 6.057073ms
      message: 'load-balancer-api-external: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 7.300055ms
      message: 'load-balancer-api-external: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:22:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "68307"
    uid: 2cf1b66c-11a2-4cef-b0ef-44665a4b6260
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:56:41Z"
      message: 'load-balancer-api-internal: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.400088ms
      message: 'load-balancer-api-internal: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:26:41Z"
    - latency: 7.499064ms
      message: 'load-balancer-api-internal: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:26:41Z"
    - latency: 3.722131ms
      message: 'load-balancer-api-internal: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 8.935587ms
      message: 'load-balancer-api-internal: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 4.706846ms
      message: 'load-balancer-api-internal: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 9.360182ms
      message: 'load-balancer-api-internal: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 4.181833ms
      message: 'load-balancer-api-internal: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 12.115659ms
      message: 'load-balancer-api-internal: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 4.947981ms
      message: 'load-balancer-api-internal: tcp connection to a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 7.382087ms
      message: 'load-balancer-api-internal: resolved host name a53e2debcb56044a59b25498c9e056b9-003fd8dee231457b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:22:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-130-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "67671"
    uid: 9c567d77-5859-46ff-a409-85793798d046
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:57:41Z"
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.502083ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 2.512277ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 2.289999ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 2.629532ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 2.244312ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:21:41Z"
    - latency: 3.495416ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:20:41Z"
    - latency: 2.512152ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:19:41Z"
    - latency: 2.579257ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:18:41Z"
    - latency: 2.607333ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:17:41Z"
    - latency: 2.031911ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:16:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-130-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "67672"
    uid: 545d5a87-5328-449c-b11c-8b14eef49e10
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:57:41Z"
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.524692ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 2.511341ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 2.502314ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 2.685975ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 2.491771ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:21:41Z"
    - latency: 2.678012ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:20:41Z"
    - latency: 2.988508ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:19:41Z"
    - latency: 2.728046ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:18:41Z"
    - latency: 2.39243ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:17:41Z"
    - latency: 2.351677ms
      message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:16:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-131-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "67670"
    uid: 545063eb-3ae9-4b32-9a3f-4a4d5c3341e0
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:57:41Z"
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024213ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 1.002286ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 1.660368ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 941.84µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 955.248µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:21:41Z"
    - latency: 2.02203ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:20:41Z"
    - latency: 1.052673ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:19:41Z"
    - latency: 1.638892ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:18:41Z"
    - latency: 1.125008ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:17:41Z"
    - latency: 930.804µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:16:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: d20cf8e9-18b9-4e3d-b52b-dab70bda0f25
    resourceVersion: "68306"
    uid: 36c9928e-8019-4409-a5ea-db895041d1e7
  spec:
    sourcePod: network-check-source-6f8b768455-ss7zp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:56:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.43809ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:26:41Z"
    - latency: 1.696141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:26:41Z"
    - latency: 988.151µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 1.957285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:25:41Z"
    - latency: 1.008747ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 1.880584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:24:41Z"
    - latency: 1.411202ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 2.188731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:23:41Z"
    - latency: 1.065798ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:22:41Z"
    - latency: 1.755179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:22:41Z"
kind: List
metadata:
  resourceVersion: ""