OSM Upgrade Troubleshooting Guide
Server could not find requested resource
If the upgrade CRD guide was not followed, it is possible that the installed CRDs are out of sync with the OSM controller.
The OSM controller will then crash with errors similar to this:
reflector.go:178] email@example.com/tools/cache/reflector.go:125: Failed to list *v1alpha2.TrafficTarget: the server could not find the requested resource (get traffictargets.access.smi-spec.io)
To resolve these errors:
- Checkout the correct release branch of the repo and run the following commands from the root.
- Delete existing CRDs and Custom Resources (TrafficTargets, TrafficSplits, etc.)
- Install the new CRDs
kubectl apply -f charts/osm/crds/
- Restart the osm-controller pod
- Recreate CustomResources
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.