apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16872"
    uid: cbb3aa14-54c9-4fa7-913b-c72418879efa
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:04:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.586308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:11:59Z"
    - latency: 809.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:10:59Z"
    - latency: 919.022µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 1.050236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 871.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 980.495µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 938.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 1.20112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:04:59Z"
    - latency: 1.408221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:03:59Z"
    - latency: 1.295597ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16073"
    uid: 1aec6c53-be57-4394-bcc4-28b22a0e9c53
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:03:59Z"
      message: 'load-balancer-api-external: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.939696ms
      message: 'load-balancer-api-external: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 6.303626ms
      message: 'load-balancer-api-external: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 5.193853ms
      message: 'load-balancer-api-external: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 6.665055ms
      message: 'load-balancer-api-external: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 4.522587ms
      message: 'load-balancer-api-external: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 8.899831ms
      message: 'load-balancer-api-external: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 5.861276ms
      message: 'load-balancer-api-external: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 6.719549ms
      message: 'load-balancer-api-external: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 3.997546ms
      message: 'load-balancer-api-external: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 6.380783ms
      message: 'load-balancer-api-external: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:05:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16072"
    uid: f54feb57-fc00-4478-aa4a-8ffba5118ca3
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:03:59Z"
      message: 'load-balancer-api-internal: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.847627ms
      message: 'load-balancer-api-internal: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 6.324691ms
      message: 'load-balancer-api-internal: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 5.213288ms
      message: 'load-balancer-api-internal: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 6.575006ms
      message: 'load-balancer-api-internal: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 5.034057ms
      message: 'load-balancer-api-internal: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 8.820147ms
      message: 'load-balancer-api-internal: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 5.897928ms
      message: 'load-balancer-api-internal: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 6.590823ms
      message: 'load-balancer-api-internal: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 4.602481ms
      message: 'load-balancer-api-internal: tcp connection to af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 6.321862ms
      message: 'load-balancer-api-internal: resolved host name af98268de5bae4a9d88468b1616689f2-1e555a8792a90c0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:05:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-network-check-target-ip-10-0-132-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16871"
    uid: 039b9582-50c6-40a8-bdc9-9cd73a11d089
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:04:59Z"
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.181591ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:11:59Z"
    - latency: 1.946629ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:10:59Z"
    - latency: 1.815444ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 2.095335ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 2.016993ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 1.974412ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 2.101909ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 2.282942ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:04:59Z"
    - latency: 2.062999ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:03:59Z"
    - latency: 2.157893ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-network-check-target-ip-10-0-136-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16869"
    uid: 701cf002-2ce3-4512-bddb-904be5523917
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:04:59Z"
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.549µs
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:11:59Z"
    - latency: 1.034225ms
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:10:59Z"
    - latency: 866.268µs
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 862.874µs
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 940.975µs
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 1.250958ms
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 890.192µs
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 1.17233ms
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:04:59Z"
    - latency: 1.227499ms
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:03:59Z"
    - latency: 1.486713ms
      message: 'network-check-target-ip-10-0-136-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-network-check-target-ip-10-0-139-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16870"
    uid: 2549b4ff-7af7-4f0f-9621-bd0ec3a035ad
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:04:59Z"
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13515ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:11:59Z"
    - latency: 1.969699ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:10:59Z"
    - latency: 1.82845ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 1.676341ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 1.898177ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 1.940916ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 1.702425ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 2.039116ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:04:59Z"
    - latency: 1.78896ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:03:59Z"
    - latency: 2.169725ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:57:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-231.ec2.internal
      uid: 80dffb76-f644-4fea-aabc-a634c9aac8af
    resourceVersion: "16071"
    uid: 8db3017b-86e5-4a12-ad88-1c933b59fc71
  spec:
    sourcePod: network-check-source-7cbc45fddc-565cz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:03:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.838µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 1.777354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:09:59Z"
    - latency: 1.215305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 1.537309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:08:59Z"
    - latency: 867.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 1.608332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:07:59Z"
    - latency: 844.407µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 1.973656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:06:59Z"
    - latency: 819.884µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:05:59Z"
    - latency: 2.433152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:05:59Z"
kind: List
metadata:
  resourceVersion: ""