apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39880"
    uid: 27ceb1a4-2417-4938-8a08-7c5471cf8764
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.749219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:57Z"
    - latency: 1.01722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 1.203585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 1.022426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 1.2169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 900.782µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 1.104248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:57Z"
    - latency: 1.539192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:57Z"
    - latency: 1.626055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:57Z"
    - latency: 1.185125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39340"
    uid: 8c23040a-1e89-4c5a-b6b6-d0812a545f15
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:57Z"
      message: 'load-balancer-api-external: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.858076ms
      message: 'load-balancer-api-external: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 8.058077ms
      message: 'load-balancer-api-external: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 6.06394ms
      message: 'load-balancer-api-external: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 7.226331ms
      message: 'load-balancer-api-external: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 5.091035ms
      message: 'load-balancer-api-external: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 7.185568ms
      message: 'load-balancer-api-external: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 5.518258ms
      message: 'load-balancer-api-external: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 9.315893ms
      message: 'load-balancer-api-external: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 4.612869ms
      message: 'load-balancer-api-external: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 9.087821ms
      message: 'load-balancer-api-external: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39339"
    uid: 3d902367-fb7b-4375-befd-c46c6755c2dc
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:57Z"
      message: 'load-balancer-api-internal: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.82039ms
      message: 'load-balancer-api-internal: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 7.992028ms
      message: 'load-balancer-api-internal: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 6.147761ms
      message: 'load-balancer-api-internal: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 7.032426ms
      message: 'load-balancer-api-internal: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 5.121984ms
      message: 'load-balancer-api-internal: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 6.996848ms
      message: 'load-balancer-api-internal: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 5.527857ms
      message: 'load-balancer-api-internal: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 9.231319ms
      message: 'load-balancer-api-internal: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 4.898192ms
      message: 'load-balancer-api-internal: tcp connection to ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 8.995242ms
      message: 'load-balancer-api-internal: resolved host name ac5c30b83e9954347949124446c169a2-3a4b3c117d6901f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-ip-10-0-128-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39878"
    uid: 2faab70f-8999-49e9-b7ea-b2882676fa2e
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:57Z"
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.312805ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:57Z"
    - latency: 2.209922ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 2.499048ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 2.150043ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 2.500679ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 2.25675ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 2.309699ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:57Z"
    - latency: 2.605942ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:57Z"
    - latency: 2.143182ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:57Z"
    - latency: 2.26509ms
      message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-ip-10-0-129-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39879"
    uid: e53afc67-8b52-4e87-ba07-e0b2a0604843
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:57Z"
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.26204ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:57Z"
    - latency: 2.177946ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 2.168918ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 2.402015ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 2.370882ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 2.454098ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 2.141123ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:57Z"
    - latency: 2.280623ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:57Z"
    - latency: 2.093482ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:57Z"
    - latency: 2.371332ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-ip-10-0-130-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39877"
    uid: eee75089-c79c-4b9d-a4d7-c8db6d19075d
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:57Z"
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.37µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:57Z"
    - latency: 2.784301ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 1.072657ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 943.861µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 965.759µs
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 1.726231ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 1.570418ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:57Z"
    - latency: 2.226307ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:57Z"
    - latency: 1.443543ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:57Z"
    - latency: 1.048708ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-142.ec2.internal
      uid: dfea169e-a9be-4ebe-b066-6ee28d4fd3e1
    resourceVersion: "39338"
    uid: 3273c558-3da5-4122-8619-5bb2c7ee8888
  spec:
    sourcePod: network-check-source-6f8b768455-2hwqk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.384129ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 1.886999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:57Z"
    - latency: 887.596µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 1.819555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:57Z"
    - latency: 950.177µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 2.291707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:57Z"
    - latency: 953.561µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 3.748178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:57Z"
    - latency: 864.603µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:57Z"
    - latency: 2.001427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:57Z"
kind: List
metadata:
  resourceVersion: ""