apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "69531"
    uid: e10affea-9732-4375-b5c6-c18e74d90e4a
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:04:32Z"
    - latency: 1.0068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 1.128808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 1.248403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 845.368µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 966.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 969.119µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:58:32Z"
    - latency: 842.132µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:32Z"
    - latency: 928.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:32Z"
    - latency: 1.384127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "68629"
    uid: a6d22848-522b-423a-a416-7f47f4b65d1a
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:21:32Z"
      message: 'load-balancer-api-external: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.59562ms
      message: 'load-balancer-api-external: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 7.113495ms
      message: 'load-balancer-api-external: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 2.769964ms
      message: 'load-balancer-api-external: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 6.790603ms
      message: 'load-balancer-api-external: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 3.615593ms
      message: 'load-balancer-api-external: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 6.855271ms
      message: 'load-balancer-api-external: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 4.811035ms
      message: 'load-balancer-api-external: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 7.158907ms
      message: 'load-balancer-api-external: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 4.002022ms
      message: 'load-balancer-api-external: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 5.969181ms
      message: 'load-balancer-api-external: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:59:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "68628"
    uid: 8af11d09-4744-4600-a1fc-0ab71ff5c72c
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:21:32Z"
      message: 'load-balancer-api-internal: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.736486ms
      message: 'load-balancer-api-internal: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 7.139736ms
      message: 'load-balancer-api-internal: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 2.758781ms
      message: 'load-balancer-api-internal: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 6.857672ms
      message: 'load-balancer-api-internal: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 3.89246ms
      message: 'load-balancer-api-internal: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 6.822876ms
      message: 'load-balancer-api-internal: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 3.924448ms
      message: 'load-balancer-api-internal: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 7.287299ms
      message: 'load-balancer-api-internal: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 3.996863ms
      message: 'load-balancer-api-internal: tcp connection to aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 6.826862ms
      message: 'load-balancer-api-internal: resolved host name aaac890da1dc64b589fde5e3fe7bcfb8-6069324b962d6216.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:59:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-network-check-target-ip-10-0-140-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "69529"
    uid: b760045d-279c-46a4-b056-750cf2e7f468
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:32Z"
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.150673ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:04:32Z"
    - latency: 2.113277ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 2.473234ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 2.269059ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 1.970895ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 2.165419ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 2.138023ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:58:32Z"
    - latency: 2.190659ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:32Z"
    - latency: 2.307886ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:32Z"
    - latency: 2.256612ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-network-check-target-ip-10-0-141-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "69527"
    uid: c9e2262a-0cd4-414f-a5ef-c9a625796793
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:32Z"
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.316µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:04:32Z"
    - latency: 1.441127ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 914.226µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 905.467µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 955.903µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 988.397µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 1.087813ms
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:58:32Z"
    - latency: 914.861µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:32Z"
    - latency: 888.884µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:32Z"
    - latency: 855.142µs
      message: 'network-check-target-ip-10-0-141-49: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-network-check-target-ip-10-0-142-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "69530"
    uid: 17e4f876-75a1-44d4-877a-01558bf8eb97
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:22:32Z"
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.78279ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:04:32Z"
    - latency: 1.57931ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 2.000349ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 1.924335ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 1.686062ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 1.960993ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 1.770506ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:58:32Z"
    - latency: 2.041324ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:57:32Z"
    - latency: 1.864422ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:56:32Z"
    - latency: 2.463167ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:55:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T01:15:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-49.ec2.internal
      uid: 00450155-1098-4b60-b1dd-350edcc010cb
    resourceVersion: "68627"
    uid: c051f8c2-2b74-4c1f-9c5b-0b64f5e396df
  spec:
    sourcePod: network-check-source-7d88cb55d8-d659t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T01:21:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.812µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 2.016934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:03:32Z"
    - latency: 1.089629ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 1.851017ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:02:32Z"
    - latency: 916.873µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 2.003362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:01:32Z"
    - latency: 778.956µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 1.755938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T02:00:32Z"
    - latency: 864.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T01:59:32Z"
    - latency: 1.784527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T01:59:32Z"
kind: List
metadata:
  resourceVersion: ""