Swift rings are stored in a ConfigMap, and when adopting an existing deployment this ConfigMap is created using existing rings.
 
The ConfigMap is later on updated and the owner is properly set. However, this started to fail now with the following API error:

"message": "configmaps \"swift-ring-files\" is forbidden: cannot set an ownerRef on a resource you can't delete: , \u003cnil\u003e",

 
In fact the delete verb is not part of the role.
 
This blocks adoption and needs to be fixed.