Skip to content
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

camel-k 1.6.10 on OCP 4.12 fails #52

Open
mbaldessari opened this issue Apr 22, 2023 · 1 comment
Open

camel-k 1.6.10 on OCP 4.12 fails #52

mbaldessari opened this issue Apr 22, 2023 · 1 comment

Comments

@mbaldessari
Copy link
Contributor

This is potentially a camel-k bug, but it's not my area, so I thought I'd at least mention it here ;)
I was trying the latest bobbycar on OCP 4.12.12 and noticed the camel-k pod failing with:

{"level":"error","ts":1682181551.5962222,"logger":"cmd","msg":"manager exited non-zero","error":"no matches for kind \"CronJob\" in version \"batch/v1beta1\"","stacktrace":"github.com/apache/camel-k/pkg/cmd/operator.exitOnError\n\tgithub.com/apache/camel-k/pkg/cmd/operator/operator.go:165\ngithub.com/apache/camel-k/pkg/cmd/operator.Run\n\tgithub.com/apache/camel-k/pkg/cmd/operator/operator.go:151\ngithub.com/apache/camel-k/pkg/cmd.(*operatorCmdOptions).run\n\tgithub.com/apache/camel-k/pkg/cmd/operator.go:54\ngithub.com/apache/camel-k/vendor/github.com/spf13/cobra.(*Command).execute\n\tgithub.com/apache/camel-k/vendor/github.com/spf13/cobra/command.go:856\ngithub.com/apache/camel-k/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/apache/camel-k/vendor/github.com/spf13/cobra/command.go:960\ngithub.com/apache/camel-k/vendor/github.com/spf13/cobra.(*Command).Execute\n\tgithub.com/apache/camel-k/vendor/github.com/spf13/cobra/command.go:897\nmain.main\n\tcommand-line-arguments/main.go:47\nruntime....

I assume 1.6.10 just assumes older k8s where CronJob/v1beta1 was still a thing. It became stable with k8s 1.21. I upgraded the camel-k operator to the 1.10.x channel and the pod did come up correctly (exact version was 1.10.0+0.1679561624.p). I suppose this is a plain bug in camel-k because according to https://access.redhat.com/labs/ocpouic/?operator=red-hat-camel-k&&ocp_versions=4.10,4.11,4.12 1.6.x is still supported on 4.12.

Feel free to close this, it is more of a heads-up than anything else ;)

@ortwinschneider
Copy link
Collaborator

Thanks for the heads-up Michele.
I've also had some issues with the Camel-K operator in the past, 1.6.x was working for me though..
And 1.6 is still the version in the stable channel..
Anyways, I'll update all the operator versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants