-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubectl apply errors with resource mapping not found for name: "cronjobs.batch"
#159
Comments
Welcome @Birdrock thanks for taking the reference implementation for a spin. Sorry you ran into an issue. This is the classic defining a CRD and a resource of that CRD in the same In the apply and delete case, running the command a second time is safe and will cleanup any lingering state the first execution missed. But that's not a great experience. There are a couple options:
While I personally use kapp for everything (and what we use in CI and for builds from source), I'd lean towards the first option to make the |
A third option is to use |
/wave from the Korifi team.
When following the instructions at https://github.com/servicebinding/runtime/releases/tag/v0.1.1 and running
kubectl apply -f https://github.com/servicebinding/runtime/releases/download/v0.1.1/servicebinding-runtime-v0.1.1.yaml
, we get the following output:This exits with
1
. If we run kubectl apply again, it finishes with a0
exit code. If we then try to delete the servicebinding-runtime withkubectl delete -f https://github.com/servicebinding/runtime/releases/download/v0.1.1/servicebinding-runtime-v0.1.1.yaml
we get the following output:This has a
1
exit code.Interestingly, applying the servicebinding-runtime again to reinstall exits
0
.The text was updated successfully, but these errors were encountered: