I've seen a similar issue being a product bug back in 2022 (https://github.com/rancher/dashboard/issues/4976) but since nobody else has brought this up in this year I can probably rule out a product bug, could i get a hint on where to look - it feels like a permission issue. The cluster is a managed OVH Kubernetes on Openstack spawned from a K3S Rancher on a VM. Oh and I am able to edit / create configmaps and secrets from the same user in the same namespace just fine (the user is admin).