From 7222032f08fd3cdbe5ae585ce3f9c37cc10638bc Mon Sep 17 00:00:00 2001 From: Scot Wells Date: Sat, 19 Sep 2026 15:55:45 -0500 Subject: [PATCH] fix: drop the retired location viewer role The viewer role inherited the location viewer from two services while both served locations. Only one serves them now: the network services operator deleted its location roles when it adopted the locations service API, so the role named here no longer exists. An inherited role that is absent leaves the role unreconciled, and every assignable organization role fails its health check behind it. That reads as missing access rather than a failure, which is why it is worth removing rather than leaving to rot. Nothing is lost. The locations service role granting the same read was already listed alongside it. The location binding viewer on the owner role stays. That type is deprecated but still served, and still written by the service catalog. --- .../roles/datum-cloud-viewer.yaml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/config/assignable-organization-roles/roles/datum-cloud-viewer.yaml b/config/assignable-organization-roles/roles/datum-cloud-viewer.yaml index bc7abb3..06ca58f 100644 --- a/config/assignable-organization-roles/roles/datum-cloud-viewer.yaml +++ b/config/assignable-organization-roles/roles/datum-cloud-viewer.yaml @@ -38,9 +38,5 @@ spec: namespace: milo-system - name: compute.datumapis.com-viewer namespace: milo-system - - name: networking.datumapis.com-location-viewer - namespace: milo-system - # Locations moved to their own service. Both roles are listed while both - # groups are served; the network-services one goes when that group does. - name: locations.miloapis.com-location-viewer namespace: milo-system