apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "53908"
    uid: 7976e310-a785-488d-8c26-396e302eb8b3
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 839.309µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 1.455226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 808.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:34Z"
    - latency: 1.308839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:34Z"
    - latency: 1.091371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:34Z"
    - latency: 890.762µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:34Z"
    - latency: 1.669628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:34Z"
    - latency: 1.045428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:34Z"
    - latency: 863.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "55767"
    uid: af94430f-f023-4dd3-9d61-275537a8a9bf
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:34Z"
      message: 'load-balancer-api-external: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.72226ms
      message: 'load-balancer-api-external: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:34Z"
    - latency: 8.213402ms
      message: 'load-balancer-api-external: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:34Z"
    - latency: 3.777692ms
      message: 'load-balancer-api-external: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:34Z"
    - latency: 6.729413ms
      message: 'load-balancer-api-external: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:34Z"
    - latency: 4.549682ms
      message: 'load-balancer-api-external: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 6.861293ms
      message: 'load-balancer-api-external: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 3.74347ms
      message: 'load-balancer-api-external: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 6.765481ms
      message: 'load-balancer-api-external: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 4.583059ms
      message: 'load-balancer-api-external: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 6.775636ms
      message: 'load-balancer-api-external: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "55768"
    uid: b019ba23-9cab-4375-805f-9c9d96d1c607
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:34Z"
      message: 'load-balancer-api-internal: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.145678ms
      message: 'load-balancer-api-internal: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:34Z"
    - latency: 8.157984ms
      message: 'load-balancer-api-internal: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:34Z"
    - latency: 4.92523ms
      message: 'load-balancer-api-internal: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:34Z"
    - latency: 6.670047ms
      message: 'load-balancer-api-internal: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:34Z"
    - latency: 4.590632ms
      message: 'load-balancer-api-internal: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 6.777418ms
      message: 'load-balancer-api-internal: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 3.774165ms
      message: 'load-balancer-api-internal: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 6.792837ms
      message: 'load-balancer-api-internal: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 5.051295ms
      message: 'load-balancer-api-internal: tcp connection to a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 6.691493ms
      message: 'load-balancer-api-internal: resolved host name a199505c0be6a439b88cb3f253816281-7be4fec459c59f69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-network-check-target-ip-10-0-128-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "53907"
    uid: 8416449a-e5cf-43d2-9c8d-be112f70b286
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:34Z"
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223635ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 2.100862ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 1.721476ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 1.842864ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:34Z"
    - latency: 2.079467ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:34Z"
    - latency: 2.314622ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:34Z"
    - latency: 2.182702ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:34Z"
    - latency: 2.18286ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:34Z"
    - latency: 2.381982ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:34Z"
    - latency: 2.235739ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-network-check-target-ip-10-0-130-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "53906"
    uid: fab66b0f-ce9d-4143-88e6-aaf7bca69462
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:34Z"
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.134312ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 2.031801ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 2.147127ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 1.905554ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:34Z"
    - latency: 2.233488ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:34Z"
    - latency: 2.248754ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:34Z"
    - latency: 2.151222ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:34Z"
    - latency: 1.832701ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:34Z"
    - latency: 2.223535ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:34Z"
    - latency: 2.002086ms
      message: 'network-check-target-ip-10-0-130-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-network-check-target-ip-10-0-140-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "53905"
    uid: a5d78eea-de4f-47c7-8979-bf5281580779
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:34Z"
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.376µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 834.11µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 743.182µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 852.971µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:34Z"
    - latency: 905.184µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:34Z"
    - latency: 912.344µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:34Z"
    - latency: 1.510922ms
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:34Z"
    - latency: 849.532µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:34Z"
    - latency: 883.65µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:34Z"
    - latency: 917.516µs
      message: 'network-check-target-ip-10-0-140-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-211.ec2.internal
      uid: 490f91c4-c21f-4541-9966-75a68a8c58d3
    resourceVersion: "55766"
    uid: bbf1bc32-eb2a-4585-a657-78e8d094cb2f
  spec:
    sourcePod: network-check-source-6f8b768455-z77n9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 827.111µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:34Z"
    - latency: 2.319224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:34Z"
    - latency: 876.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:34Z"
    - latency: 1.795259ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:34Z"
    - latency: 669.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 2.430803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:34Z"
    - latency: 1.259081ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 1.776209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:34Z"
    - latency: 934.351µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:34Z"
    - latency: 2.167948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:34Z"
kind: List
metadata:
  resourceVersion: ""