apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64861"
    uid: f72eb0be-d7d7-4c0e-8514-a6a55c9b6d83
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:18:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.704024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 813.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 1.24079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 1.324621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 1.114655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 905.516µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:48:46Z"
    - latency: 1.13309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:47:46Z"
    - latency: 1.138423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:46:46Z"
    - latency: 1.453074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:45:46Z"
    - latency: 1.019592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64862"
    uid: 7cf33535-2033-4d13-8f04-9de60f0bc478
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:17:46Z"
      message: 'load-balancer-api-external: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.19689ms
      message: 'load-balancer-api-external: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 6.958731ms
      message: 'load-balancer-api-external: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 4.801637ms
      message: 'load-balancer-api-external: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 7.019396ms
      message: 'load-balancer-api-external: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 4.437484ms
      message: 'load-balancer-api-external: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 6.367268ms
      message: 'load-balancer-api-external: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 3.298271ms
      message: 'load-balancer-api-external: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 6.313624ms
      message: 'load-balancer-api-external: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 5.01871ms
      message: 'load-balancer-api-external: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 6.57098ms
      message: 'load-balancer-api-external: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:49:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64863"
    uid: 90c19733-9d76-45f2-adb9-d1cbbd61cf75
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:17:46Z"
      message: 'load-balancer-api-internal: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.936717ms
      message: 'load-balancer-api-internal: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 6.920946ms
      message: 'load-balancer-api-internal: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 4.762049ms
      message: 'load-balancer-api-internal: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 7.096821ms
      message: 'load-balancer-api-internal: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 4.337002ms
      message: 'load-balancer-api-internal: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 6.427548ms
      message: 'load-balancer-api-internal: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 3.196405ms
      message: 'load-balancer-api-internal: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 6.39186ms
      message: 'load-balancer-api-internal: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 3.28825ms
      message: 'load-balancer-api-internal: tcp connection to a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 6.529661ms
      message: 'load-balancer-api-internal: resolved host name a78a2b258d0d44211a59f503698ad274-22929661d09cff1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:49:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-network-check-target-ip-10-0-135-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64857"
    uid: 10e08bdc-dcc3-43a9-92ec-541850cb08fa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:18:46Z"
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.439µs
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 1.040553ms
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 955.407µs
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 833.638µs
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 1.274906ms
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 797.224µs
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:48:46Z"
    - latency: 774.016µs
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:47:46Z"
    - latency: 1.081409ms
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:46:46Z"
    - latency: 1.241583ms
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:45:46Z"
    - latency: 862.799µs
      message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-network-check-target-ip-10-0-137-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64858"
    uid: d72a1afc-ab8c-4638-aada-144debef825d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:18:46Z"
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.911919ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 1.833294ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 1.97403ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 1.879158ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 2.004059ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 1.841815ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:48:46Z"
    - latency: 1.944271ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:47:46Z"
    - latency: 1.997803ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:46:46Z"
    - latency: 1.874711ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:45:46Z"
    - latency: 1.87333ms
      message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-network-check-target-ip-10-0-138-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64859"
    uid: e1fe4c39-9d8d-4173-9302-ab4cb5211920
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:18:46Z"
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297118ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 2.217948ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 2.362384ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 2.18342ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 2.478493ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 2.437828ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:48:46Z"
    - latency: 2.303423ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:47:46Z"
    - latency: 2.348729ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:46:46Z"
    - latency: 2.136689ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:45:46Z"
    - latency: 2.382693ms
      message: 'network-check-target-ip-10-0-138-182: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:44:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-163-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-163.ec2.internal
      uid: f202dd61-37d5-4ffa-9fa5-5e7d9404d110
    resourceVersion: "64860"
    uid: f2f62d2a-d011-4ad7-aec5-9c651bdbdccd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kcrvs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:17:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.209748ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 1.757397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:53:46Z"
    - latency: 1.188408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 1.752976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:52:46Z"
    - latency: 1.217232ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 1.75541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:51:46Z"
    - latency: 1.151882ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 1.627185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:50:46Z"
    - latency: 910.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:49:46Z"
    - latency: 1.951962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T00:49:46Z"
kind: List
metadata:
  resourceVersion: ""