apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "62320"
    uid: c5e6363b-7bcc-4afc-9f0c-7a4037dad224
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:16:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:55:01Z"
    - latency: 1.319336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 894.481µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 1.368407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 1.150528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 1.231076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 1.245752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:49:01Z"
    - latency: 1.05713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:48:01Z"
    - latency: 1.453717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
    - latency: 1.453717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "61483"
    uid: 1a445d40-fbda-41c1-9ddf-538cbb695599
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:15:01Z"
      message: 'load-balancer-api-external: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.463965ms
      message: 'load-balancer-api-external: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 7.754313ms
      message: 'load-balancer-api-external: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 5.578677ms
      message: 'load-balancer-api-external: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 11.118293ms
      message: 'load-balancer-api-external: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 4.682612ms
      message: 'load-balancer-api-external: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 7.975301ms
      message: 'load-balancer-api-external: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 5.995263ms
      message: 'load-balancer-api-external: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 7.549935ms
      message: 'load-balancer-api-external: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 4.770244ms
      message: 'load-balancer-api-external: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 6.609135ms
      message: 'load-balancer-api-external: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:50:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "61484"
    uid: 720cbb41-c01c-4327-bbb2-5918f019696e
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:15:01Z"
      message: 'load-balancer-api-internal: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.934741ms
      message: 'load-balancer-api-internal: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 7.730006ms
      message: 'load-balancer-api-internal: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 4.416147ms
      message: 'load-balancer-api-internal: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 11.149557ms
      message: 'load-balancer-api-internal: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 5.269925ms
      message: 'load-balancer-api-internal: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 8.006849ms
      message: 'load-balancer-api-internal: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 6.234449ms
      message: 'load-balancer-api-internal: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 7.585991ms
      message: 'load-balancer-api-internal: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 3.815294ms
      message: 'load-balancer-api-internal: tcp connection to a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 6.662314ms
      message: 'load-balancer-api-internal: resolved host name a2ac533c556b142cd9591e189ecb12d9-8c212c476a1563ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:50:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-network-check-target-ip-10-0-130-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "62319"
    uid: 60fc5697-aba8-4ae2-860d-7825c0d9df69
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:16:01Z"
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.035509ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:55:01Z"
    - latency: 1.956792ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 2.023907ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 2.193826ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 2.078215ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 2.054172ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 2.303056ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:49:01Z"
    - latency: 2.11499ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:48:01Z"
    - latency: 2.109966ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
    - latency: 2.109966ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-network-check-target-ip-10-0-132-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "62317"
    uid: dc8d21e3-6d78-412f-8eb1-f7ea6b3540af
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:16:01Z"
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.884662ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:55:01Z"
    - latency: 2.341272ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 2.424711ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 2.329698ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 2.38073ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 2.349208ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 2.253392ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:49:01Z"
    - latency: 2.251504ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:48:01Z"
    - latency: 3.03157ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
    - latency: 3.03157ms
      message: 'network-check-target-ip-10-0-132-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-network-check-target-ip-10-0-135-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "62318"
    uid: d5b5c56e-e848-4e7c-8780-90961ccc62a4
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:16:01Z"
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.059µs
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:55:01Z"
    - latency: 1.500089ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 1.129497ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 1.009015ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 1.260238ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 821.616µs
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 951.038µs
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:49:01Z"
    - latency: 1.283688ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:48:01Z"
    - latency: 1.669678ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
    - latency: 1.669678ms
      message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:47:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T16:09:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-253.ec2.internal
      uid: ffbea164-8091-435d-adf2-25be2b5ecea6
    resourceVersion: "61480"
    uid: 810e52c1-5780-49a6-be23-77909114f3fc
  spec:
    sourcePod: network-check-source-7cbc45fddc-9cjph
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T16:15:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 2.344286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:54:01Z"
    - latency: 1.080523ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 1.875864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:53:01Z"
    - latency: 865.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 1.959293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:52:01Z"
    - latency: 851.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 1.875451ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:51:01Z"
    - latency: 1.251386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:50:01Z"
    - latency: 2.01562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:50:01Z"
kind: List
metadata:
  resourceVersion: ""