kragniz / kragniz/tor-controller
error: unable to recognize "install.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta"
- Dominant language
- Go
- Stars
- 532
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
CustomResourceDefinition is outdated.
```
kubectl apply -f install.yaml
```
Output:
```
error: unable to recognize "install.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta"
```
Tried to use ```kubectl convert``` but does not work
```
kubectl convert -f install.yaml
```
Output:
```
error: unable to decode "install.yaml": no kind "CustomResourceDefinition" is registered for version "apiextensions.k8s.io/v1beta" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with install.yaml and inspect the CustomResourceDefinition declaration using the apiextensions.k8s.io/v1beta version shown in the error. Run kubectl apply -f install.yaml to reproduce the failure, then verify that the manifest is accepted without the reported version error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100