apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32282"
    uid: 7fb26b1e-4416-4cda-8220-34e88a99952f
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.403424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 954.526µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 1.06964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 1.095237ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 1.117087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 879.023µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:42Z"
    - latency: 1.032604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:42Z"
    - latency: 1.079822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:42Z"
    - latency: 895.072µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:42Z"
    - latency: 1.235833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32284"
    uid: 50910637-2f8c-423b-8d31-051c2b25377a
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:42Z"
      message: 'load-balancer-api-external: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.305297ms
      message: 'load-balancer-api-external: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 8.250603ms
      message: 'load-balancer-api-external: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 5.153101ms
      message: 'load-balancer-api-external: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 8.047358ms
      message: 'load-balancer-api-external: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 5.106975ms
      message: 'load-balancer-api-external: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 8.081763ms
      message: 'load-balancer-api-external: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 5.234985ms
      message: 'load-balancer-api-external: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 8.759513ms
      message: 'load-balancer-api-external: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 5.021198ms
      message: 'load-balancer-api-external: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 8.451806ms
      message: 'load-balancer-api-external: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:16:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32283"
    uid: dfd0714c-248b-40ea-bfcc-4a62f83dac18
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:42Z"
      message: 'load-balancer-api-internal: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.83301ms
      message: 'load-balancer-api-internal: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 8.303762ms
      message: 'load-balancer-api-internal: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 5.206919ms
      message: 'load-balancer-api-internal: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 8.016341ms
      message: 'load-balancer-api-internal: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 5.118548ms
      message: 'load-balancer-api-internal: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 8.122149ms
      message: 'load-balancer-api-internal: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 5.62123ms
      message: 'load-balancer-api-internal: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 8.715591ms
      message: 'load-balancer-api-internal: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 5.033772ms
      message: 'load-balancer-api-internal: tcp connection to af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 8.418285ms
      message: 'load-balancer-api-internal: resolved host name af06ee4b56e174781bba839d6a67236c-e8be350dadd6c35c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:16:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-network-check-target-ip-10-0-128-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32278"
    uid: 71a92ba0-913e-4b5f-bfeb-082387a4a004
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:42Z"
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.76275ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 1.086972ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 857.6µs
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 926.415µs
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 1.030782ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 741.086µs
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:42Z"
    - latency: 1.267229ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:42Z"
    - latency: 1.158183ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:42Z"
    - latency: 1.484238ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:42Z"
    - latency: 1.11198ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-network-check-target-ip-10-0-132-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32280"
    uid: 56324fe5-1d51-4f79-b19f-b01452209fe1
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:42Z"
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.842623ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 1.639045ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 1.994329ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 1.933606ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 1.963776ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 1.775602ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:42Z"
    - latency: 1.965503ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:42Z"
    - latency: 2.169487ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:42Z"
    - latency: 1.925069ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:42Z"
    - latency: 2.095034ms
      message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-network-check-target-ip-10-0-137-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32281"
    uid: e442ae20-a2b5-47f0-b1b9-b0f0de4886c6
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:42Z"
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.63104ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 2.036535ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 2.157436ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 1.938366ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 2.211288ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 2.135895ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:15:42Z"
    - latency: 2.15916ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:14:42Z"
    - latency: 2.124868ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:13:42Z"
    - latency: 2.271569ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:12:42Z"
    - latency: 2.36483ms
      message: 'network-check-target-ip-10-0-137-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-248-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-248.ec2.internal
      uid: 9da60210-b033-4852-9fe6-623419925dd1
    resourceVersion: "32279"
    uid: bbd35ccf-10eb-4097-90b9-92b028dea516
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kvhf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 733.207µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 2.04705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:20:42Z"
    - latency: 875.76µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 1.637228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:19:42Z"
    - latency: 745.638µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 1.609056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:18:42Z"
    - latency: 885.841µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 1.770523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:17:42Z"
    - latency: 952.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:42Z"
    - latency: 1.90935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:16:42Z"
kind: List
metadata:
  resourceVersion: ""