apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "69172"
    uid: a16768df-7855-4466-9362-8ae793795329
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:56:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.387687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 1.108122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 1.115663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 1.25725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 1.141929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:20:08Z"
    - latency: 1.724557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:19:08Z"
    - latency: 997.048µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:18:08Z"
    - latency: 1.043926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:17:08Z"
    - latency: 1.015784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:16:08Z"
    - latency: 915.228µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:15:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "70130"
    uid: 7ce7ad9d-ee69-4384-8211-08f515ca56fb
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:55:08Z"
      message: 'load-balancer-api-external: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.250348ms
      message: 'load-balancer-api-external: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:25:08Z"
    - latency: 10.161548ms
      message: 'load-balancer-api-external: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:25:08Z"
    - latency: 4.165726ms
      message: 'load-balancer-api-external: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 7.17605ms
      message: 'load-balancer-api-external: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 4.398607ms
      message: 'load-balancer-api-external: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 7.712917ms
      message: 'load-balancer-api-external: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 4.884486ms
      message: 'load-balancer-api-external: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 6.93009ms
      message: 'load-balancer-api-external: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 4.642109ms
      message: 'load-balancer-api-external: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 8.404458ms
      message: 'load-balancer-api-external: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:21:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "70131"
    uid: f45551ac-8119-4c9c-91f8-745610bd9ee5
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:55:08Z"
      message: 'load-balancer-api-internal: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.240572ms
      message: 'load-balancer-api-internal: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:25:08Z"
    - latency: 10.241106ms
      message: 'load-balancer-api-internal: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:25:08Z"
    - latency: 4.182407ms
      message: 'load-balancer-api-internal: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 7.155495ms
      message: 'load-balancer-api-internal: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 4.405063ms
      message: 'load-balancer-api-internal: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 7.749447ms
      message: 'load-balancer-api-internal: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 3.9234ms
      message: 'load-balancer-api-internal: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 6.905073ms
      message: 'load-balancer-api-internal: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 4.498555ms
      message: 'load-balancer-api-internal: tcp connection to a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 8.467041ms
      message: 'load-balancer-api-internal: resolved host name a58ca3428775740c697debf4d8f5ccb2-7e5e8fd218191148.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:21:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-network-check-target-ip-10-0-128-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "69170"
    uid: 3791f006-9b32-4b41-97f1-97d90a4039c5
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:56:08Z"
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99791ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 2.261341ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 2.203257ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 2.181138ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 2.604046ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:20:08Z"
    - latency: 2.458802ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:19:08Z"
    - latency: 2.240336ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:18:08Z"
    - latency: 1.98737ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:17:08Z"
    - latency: 2.224813ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:16:08Z"
    - latency: 2.012613ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:15:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-network-check-target-ip-10-0-133-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "69171"
    uid: b1592eec-5043-475d-9f90-9080a53d6ac2
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:56:08Z"
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.071398ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 2.105465ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 1.926741ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 2.304984ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 2.098003ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:20:08Z"
    - latency: 2.053888ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:19:08Z"
    - latency: 1.776761ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:18:08Z"
    - latency: 2.490557ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:17:08Z"
    - latency: 2.75299ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:16:08Z"
    - latency: 1.786183ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:15:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-network-check-target-ip-10-0-143-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "69168"
    uid: 65b7964b-dc58-4401-9a3b-4ea70b4137ad
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:56:08Z"
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033109ms
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 859.98µs
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 890.782µs
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 1.152317ms
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 909.5µs
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:20:08Z"
    - latency: 1.432826ms
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:19:08Z"
    - latency: 945.8µs
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:18:08Z"
    - latency: 1.147807ms
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:17:08Z"
    - latency: 796.264µs
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:16:08Z"
    - latency: 1.182495ms
      message: 'network-check-target-ip-10-0-143-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:15:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T01:49:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-251-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-251.ec2.internal
      uid: abeddcc7-b976-4315-b49c-1c8d2c9c0895
    resourceVersion: "70129"
    uid: d0f327c4-a9b3-49a9-9558-c905a8ea99df
  spec:
    sourcePod: network-check-source-6f8b768455-x49c5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T01:55:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.264401ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:25:08Z"
    - latency: 1.792398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:25:08Z"
    - latency: 947.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 2.124444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:24:08Z"
    - latency: 1.26858ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 1.751761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:23:08Z"
    - latency: 1.173592ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 1.923444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:22:08Z"
    - latency: 1.635742ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T02:21:08Z"
    - latency: 1.948197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T02:21:08Z"
kind: List
metadata:
  resourceVersion: ""