apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "38400"
    uid: 51b72120-860f-4a0a-8ebb-c48060a956a4
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:09:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.418709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:51:50Z"
    - latency: 1.029522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 796.988µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 1.083976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 1.375214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 1.335806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 837.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:45:50Z"
    - latency: 856.885µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:44:50Z"
    - latency: 1.012962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:43:50Z"
    - latency: 1.004271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:42:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "37848"
    uid: 84dbe05e-183f-4046-88bd-4700eb653a56
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:08:50Z"
      message: 'load-balancer-api-external: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.660197ms
      message: 'load-balancer-api-external: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 6.50902ms
      message: 'load-balancer-api-external: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 5.424911ms
      message: 'load-balancer-api-external: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 8.420337ms
      message: 'load-balancer-api-external: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 6.333383ms
      message: 'load-balancer-api-external: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 8.348054ms
      message: 'load-balancer-api-external: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 5.261272ms
      message: 'load-balancer-api-external: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 7.043061ms
      message: 'load-balancer-api-external: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 3.692687ms
      message: 'load-balancer-api-external: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 8.65355ms
      message: 'load-balancer-api-external: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:46:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "37849"
    uid: cdbcef05-eee3-491b-89b4-c6bdd1c550d2
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:08:50Z"
      message: 'load-balancer-api-internal: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.613137ms
      message: 'load-balancer-api-internal: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 6.47547ms
      message: 'load-balancer-api-internal: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 5.431729ms
      message: 'load-balancer-api-internal: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 8.356769ms
      message: 'load-balancer-api-internal: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 5.554957ms
      message: 'load-balancer-api-internal: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 8.313716ms
      message: 'load-balancer-api-internal: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 5.284219ms
      message: 'load-balancer-api-internal: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 7.015922ms
      message: 'load-balancer-api-internal: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 3.915156ms
      message: 'load-balancer-api-internal: tcp connection to a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 8.611793ms
      message: 'load-balancer-api-internal: resolved host name a1eb58230b231440ea7d062e6582c108-f731a9b052801103.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:46:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-ip-10-0-129-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "38397"
    uid: b61e7e74-c33e-4311-a692-dc958c066a2f
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:09:50Z"
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 772.072µs
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:51:50Z"
    - latency: 940.975µs
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 1.000067ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 1.108826ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 1.564478ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 810.246µs
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 1.404373ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:45:50Z"
    - latency: 1.003559ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:44:50Z"
    - latency: 906.902µs
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:43:50Z"
    - latency: 1.095664ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:42:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-ip-10-0-132-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "38399"
    uid: 95ab5319-15f0-44b9-9600-8e5b9b928214
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:09:50Z"
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.17613ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:51:50Z"
    - latency: 2.478925ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 2.449986ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 2.308409ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 2.300703ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 2.380988ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 2.374483ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:45:50Z"
    - latency: 2.432923ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:44:50Z"
    - latency: 2.359427ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:43:50Z"
    - latency: 2.182311ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:42:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-ip-10-0-132-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "38398"
    uid: fe249a17-7a89-45ed-851a-4347f56b4668
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:09:50Z"
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.633419ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:51:50Z"
    - latency: 1.945214ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 1.904408ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 1.759407ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 1.886213ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 2.065497ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 2.203891ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:45:50Z"
    - latency: 1.87328ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:44:50Z"
    - latency: 2.014542ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:43:50Z"
    - latency: 2.055412ms
      message: 'network-check-target-ip-10-0-132-242: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:42:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T18:02:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: f8cdf227-5e0a-48ec-8d77-a19b86722d27
    resourceVersion: "37846"
    uid: aeec7d0d-67e8-4aec-8bd7-79f6a4cd50e1
  spec:
    sourcePod: network-check-source-65bdbbff45-vl78f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T18:08:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 1.553965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:50:50Z"
    - latency: 800.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 1.782079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:49:50Z"
    - latency: 912.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 1.948379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:48:50Z"
    - latency: 853.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 1.794193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:47:50Z"
    - latency: 685.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T18:46:50Z"
    - latency: 2.020418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T18:46:50Z"
kind: List
metadata:
  resourceVersion: ""