everettraven / everettraven/telescopia
Add custom errors to differentiate between errors from the cache and the kube apiserver
- Dominant language
- Go
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
## Description
We need to implement custom errors that allows operator authors to determine whether an error is coming from the dynamic cache vs the Kubernetes apiserver.
For example, the dynamic cache could return a Kubernetes `NotFound` error but in the context of the dynamic cache this `NotFound` error could represent that the requested resource does not exist on the cluster OR that an informer with the configuration to find that resource does not exist. In the latter case the resource may exist on the cluster but was never populated into the cache and therefore the dynamic cache cannot find it.
There is already some [existing custom errors](https://github.com/everettraven/telescopia/blob/main/pkg/cache/components.go#L175-L229) but we need to ensure they are implemented properly and actually being returned by the dynamic cache.
## Acceptance Criteria
- Create/Update custom errors as necessary
- Update the cache implementation to return the custom errors as appropriate
- Unit tests
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.