apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "44037"
    uid: 4c540128-6660-49f6-a825-b3059f11de8c
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:00:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.118932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 1.129221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 891.284µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 1.030818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:18:15Z"
    - latency: 1.17143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:17:15Z"
    - latency: 999.57µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:16:15Z"
    - latency: 1.09213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:15:15Z"
    - latency: 891.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:14:15Z"
    - latency: 886.355µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:13:15Z"
    - latency: 875.644µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:12:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "46039"
    uid: 923b6353-21b5-49e0-bf4f-22d65a25bde7
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T21:59:15Z"
      message: 'load-balancer-api-external: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.171395ms
      message: 'load-balancer-api-external: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:23:15Z"
    - latency: 6.316006ms
      message: 'load-balancer-api-external: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:23:15Z"
    - latency: 5.198254ms
      message: 'load-balancer-api-external: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:22:15Z"
    - latency: 6.829521ms
      message: 'load-balancer-api-external: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:22:15Z"
    - latency: 4.753036ms
      message: 'load-balancer-api-external: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 6.669872ms
      message: 'load-balancer-api-external: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 4.508087ms
      message: 'load-balancer-api-external: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 6.737763ms
      message: 'load-balancer-api-external: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 4.84089ms
      message: 'load-balancer-api-external: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 6.855624ms
      message: 'load-balancer-api-external: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:19:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "46040"
    uid: 3a78a0b0-aa71-47c9-a423-d07d980814f3
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T21:59:15Z"
      message: 'load-balancer-api-internal: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.175015ms
      message: 'load-balancer-api-internal: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:23:15Z"
    - latency: 6.305449ms
      message: 'load-balancer-api-internal: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:23:15Z"
    - latency: 4.461944ms
      message: 'load-balancer-api-internal: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:22:15Z"
    - latency: 6.851419ms
      message: 'load-balancer-api-internal: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:22:15Z"
    - latency: 4.687285ms
      message: 'load-balancer-api-internal: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 6.764888ms
      message: 'load-balancer-api-internal: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 3.93588ms
      message: 'load-balancer-api-internal: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 6.666723ms
      message: 'load-balancer-api-internal: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 4.787743ms
      message: 'load-balancer-api-internal: tcp connection to a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 7.00197ms
      message: 'load-balancer-api-internal: resolved host name a674d0d00f6db49878ff1bb725ab8380-829cd3a801cde4cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:19:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-network-check-target-ip-10-0-136-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "44034"
    uid: 9d2e174e-2d79-483f-8b16-de685a3e5469
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:00:15Z"
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.795µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 1.102294ms
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 752.882µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 904.83µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:18:15Z"
    - latency: 1.064257ms
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:17:15Z"
    - latency: 786.827µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:16:15Z"
    - latency: 852.231µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:15:15Z"
    - latency: 890.635µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:14:15Z"
    - latency: 1.405043ms
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:13:15Z"
    - latency: 935.033µs
      message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:12:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-network-check-target-ip-10-0-137-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "44036"
    uid: f7a1af7a-8344-4bb2-8083-7adc04ca05ca
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:00:15Z"
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.314727ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 2.728675ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 2.355666ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 2.37173ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:18:15Z"
    - latency: 2.508872ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:17:15Z"
    - latency: 2.267583ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:16:15Z"
    - latency: 2.149149ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:15:15Z"
    - latency: 2.597073ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:14:15Z"
    - latency: 2.282328ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:13:15Z"
    - latency: 2.068617ms
      message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:12:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-network-check-target-ip-10-0-140-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "44035"
    uid: b841441d-6ff3-476e-be28-44cafcdf5ba4
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:00:15Z"
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.108827ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 2.222219ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 2.35129ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 2.248115ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:18:15Z"
    - latency: 2.354128ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:17:15Z"
    - latency: 2.031086ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:16:15Z"
    - latency: 2.128412ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:15:15Z"
    - latency: 2.224432ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:14:15Z"
    - latency: 1.957559ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:13:15Z"
    - latency: 2.166718ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:12:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T21:53:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-102.ec2.internal
      uid: 90c2ddb4-7153-4fb9-97d1-dbc5a194747c
    resourceVersion: "46038"
    uid: c43ff8bd-e4c7-4a9d-bba6-fda9918b3600
  spec:
    sourcePod: network-check-source-8894fc9bd-l59hp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T21:59:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:23:15Z"
    - latency: 1.72741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:23:15Z"
    - latency: 1.07301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:22:15Z"
    - latency: 1.699836ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:22:15Z"
    - latency: 833.912µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 1.677026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:21:15Z"
    - latency: 1.023739ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 1.834613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:20:15Z"
    - latency: 1.099202ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:19:15Z"
    - latency: 2.233619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:19:15Z"
kind: List
metadata:
  resourceVersion: ""