Skip to content

Commit

Permalink
docs(upgrade): Add upgrade troubleshooting guide (openservicemesh#2377)
Browse files Browse the repository at this point in the history
Signed-off-by: Kalya Subramanian <kasubra@microsoft.com>
  • Loading branch information
ksubrmnn authored Jan 26, 2021
1 parent ddcdb0f commit 853b995
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions docs/troubleshooting/upgrade.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# OSM Upgrade Troubleshooting Guide

## Server could not find requested resource
If the [upgrade CRD guide](../upgrade_guide.md##crd-upgrades) 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] pkg/mod/k8s.io/client-go@v0.18.6/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:
1. Checkout the correct release branch of the [repo](https://github.com/openservicemesh/osm) and run the following commands from the root.
1. Delete existing CRDs and Custom Resources (TrafficTargets, TrafficSplits, etc.)
- `./scripts/cleanup/crd-cleanup.sh`
1. Install the new CRDs
- `kubectl apply -f charts/osm/crds/`
1. Restart the osm-controller pod
1. Recreate CustomResources

0 comments on commit 853b995

Please sign in to comment.