apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "24738"
    uid: 1084212e-e415-4e86-9aae-40bec958c0df
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:59:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:27:47Z"
    - latency: 770.417µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:26:47Z"
    - latency: 916.828µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:25:47Z"
    - latency: 1.32716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:24:47Z"
    - latency: 1.026532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:23:47Z"
    - latency: 1.042999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 1.107016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 1.239644ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 1.120809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 1.065904ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "22826"
    uid: b0012321-e80d-4168-87b1-78ffd41a8e4f
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:58:47Z"
      message: 'load-balancer-api-external: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.667009ms
      message: 'load-balancer-api-external: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 8.004814ms
      message: 'load-balancer-api-external: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 5.44108ms
      message: 'load-balancer-api-external: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 8.793157ms
      message: 'load-balancer-api-external: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 4.453408ms
      message: 'load-balancer-api-external: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 8.607002ms
      message: 'load-balancer-api-external: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 5.17229ms
      message: 'load-balancer-api-external: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 8.053503ms
      message: 'load-balancer-api-external: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 6.200551ms
      message: 'load-balancer-api-external: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
    - latency: 14.584938ms
      message: 'load-balancer-api-external: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "22827"
    uid: 99e320f6-95b8-4d8b-a1ef-418bf2425560
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:58:47Z"
      message: 'load-balancer-api-internal: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.601523ms
      message: 'load-balancer-api-internal: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 7.975806ms
      message: 'load-balancer-api-internal: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 4.878381ms
      message: 'load-balancer-api-internal: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 8.761017ms
      message: 'load-balancer-api-internal: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 4.982174ms
      message: 'load-balancer-api-internal: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 8.54838ms
      message: 'load-balancer-api-internal: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 5.077103ms
      message: 'load-balancer-api-internal: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 8.037238ms
      message: 'load-balancer-api-internal: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 6.247814ms
      message: 'load-balancer-api-internal: tcp connection to a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
    - latency: 14.617299ms
      message: 'load-balancer-api-internal: resolved host name a06a4564594a745949da182889c168e1-ee8d086a8de6f335.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-131-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "24737"
    uid: a1194dc3-37ba-4890-b7ad-85e46e1305b1
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:59:47Z"
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.704221ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:27:47Z"
    - latency: 1.780856ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:26:47Z"
    - latency: 1.851196ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:25:47Z"
    - latency: 1.81458ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:24:47Z"
    - latency: 1.941629ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:23:47Z"
    - latency: 1.894632ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 2.232468ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 2.30564ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 1.726167ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 1.744117ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-139-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "24735"
    uid: da3c6e46-a52a-4d28-a9b0-77dfc626a12b
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:59:47Z"
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.263048ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:27:47Z"
    - latency: 705.717µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:26:47Z"
    - latency: 687.822µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:25:47Z"
    - latency: 1.310549ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:24:47Z"
    - latency: 822.625µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:23:47Z"
    - latency: 820.443µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 822.476µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 765.619µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 788.155µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 865.846µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-141-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "24736"
    uid: 364fae42-4a0b-4f99-bc5c-1c902dbb4d37
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:59:47Z"
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.799851ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:27:47Z"
    - latency: 1.90419ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:26:47Z"
    - latency: 1.709237ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:25:47Z"
    - latency: 2.158593ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:24:47Z"
    - latency: 2.229841ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:23:47Z"
    - latency: 2.41841ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 2.143047ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 2.416665ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 1.763089ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 2.204044ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:52:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: 9d2c5174-eebe-4164-9175-7be9287aa00e
    resourceVersion: "22825"
    uid: 044d0019-7848-4775-92f1-952b24761846
  spec:
    sourcePod: network-check-source-8894fc9bd-wttb6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T08:58:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 678.525µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 1.5704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:22:47Z"
    - latency: 928.946µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 1.674742ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:21:47Z"
    - latency: 1.219215ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 1.697076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:20:47Z"
    - latency: 963.548µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 1.732499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:19:47Z"
    - latency: 782.225µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:18:47Z"
    - latency: 1.599813ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:18:47Z"
kind: List
metadata:
  resourceVersion: ""