apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "45844"
    uid: 7d0b4902-a3e6-413f-b0bb-87c25356b613
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:29:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.348064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 940.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 1.243186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 923.847µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:47:14Z"
    - latency: 972.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:46:14Z"
    - latency: 1.368972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:45:14Z"
    - latency: 919.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:44:14Z"
    - latency: 1.617786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:43:14Z"
    - latency: 1.120437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:42:14Z"
    - latency: 1.332506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:41:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "48148"
    uid: 945b41bf-308c-46eb-902e-36a5af9e9a48
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:28:14Z"
      message: 'load-balancer-api-external: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.901644ms
      message: 'load-balancer-api-external: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:52:14Z"
    - latency: 13.191338ms
      message: 'load-balancer-api-external: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:52:14Z"
    - latency: 3.956669ms
      message: 'load-balancer-api-external: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:51:14Z"
    - latency: 16.572423ms
      message: 'load-balancer-api-external: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:51:14Z"
    - latency: 4.076317ms
      message: 'load-balancer-api-external: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 8.807744ms
      message: 'load-balancer-api-external: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 4.014241ms
      message: 'load-balancer-api-external: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 7.916122ms
      message: 'load-balancer-api-external: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 5.331407ms
      message: 'load-balancer-api-external: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 8.326258ms
      message: 'load-balancer-api-external: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:48:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "48147"
    uid: 325759e3-3456-49d2-873e-837f466a8333
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:28:14Z"
      message: 'load-balancer-api-internal: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.905105ms
      message: 'load-balancer-api-internal: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:52:14Z"
    - latency: 13.297438ms
      message: 'load-balancer-api-internal: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:52:14Z"
    - latency: 3.951901ms
      message: 'load-balancer-api-internal: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:51:14Z"
    - latency: 16.715558ms
      message: 'load-balancer-api-internal: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:51:14Z"
    - latency: 4.33567ms
      message: 'load-balancer-api-internal: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 8.87951ms
      message: 'load-balancer-api-internal: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 3.727766ms
      message: 'load-balancer-api-internal: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 7.87657ms
      message: 'load-balancer-api-internal: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 4.96833ms
      message: 'load-balancer-api-internal: tcp connection to a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 8.411676ms
      message: 'load-balancer-api-internal: resolved host name a947037bd53824628ae42b57163a5eaa-59ce9807377b5b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:48:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-network-check-target-ip-10-0-128-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "45841"
    uid: ebc9c4b9-6b75-4d27-b360-55aec51b727f
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:29:14Z"
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.432495ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 893.164µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 967.72µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 922.938µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:47:14Z"
    - latency: 974.953µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:46:14Z"
    - latency: 1.499218ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:45:14Z"
    - latency: 1.566664ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:44:14Z"
    - latency: 842.318µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:43:14Z"
    - latency: 883.202µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:42:14Z"
    - latency: 978.103µs
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:41:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-network-check-target-ip-10-0-134-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "45842"
    uid: 1f8370f8-adf4-4b3f-bd30-364253fa51ea
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:29:14Z"
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.021548ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 1.906961ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 1.781471ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 1.73825ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:47:14Z"
    - latency: 1.71306ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:46:14Z"
    - latency: 1.901455ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:45:14Z"
    - latency: 1.801419ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:44:14Z"
    - latency: 1.933524ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:43:14Z"
    - latency: 1.633742ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:42:14Z"
    - latency: 1.704177ms
      message: 'network-check-target-ip-10-0-134-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:41:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-network-check-target-ip-10-0-134-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "45843"
    uid: 1179738b-06e4-4d26-b903-711e94d612ff
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:29:14Z"
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.531679ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 2.03609ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 2.201601ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 2.042429ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:47:14Z"
    - latency: 2.28601ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:46:14Z"
    - latency: 2.175078ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:45:14Z"
    - latency: 2.382791ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:44:14Z"
    - latency: 2.239853ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:43:14Z"
    - latency: 2.200968ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:42:14Z"
    - latency: 2.116351ms
      message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:41:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T03:22:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-105.ec2.internal
      uid: e4cf576d-c0e5-4b90-b473-3b4b06903284
    resourceVersion: "48146"
    uid: fd9775f6-06db-43c4-b30d-c79b0eac3b91
  spec:
    sourcePod: network-check-source-6947749cfc-b2qwf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T03:28:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.303371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:52:14Z"
    - latency: 1.707006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:52:14Z"
    - latency: 711.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:51:14Z"
    - latency: 2.086029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:51:14Z"
    - latency: 919.831µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 1.819126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:50:14Z"
    - latency: 784µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 2.14715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:49:14Z"
    - latency: 935.44µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T03:48:14Z"
    - latency: 1.817581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T03:48:14Z"
kind: List
metadata:
  resourceVersion: ""