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 ;)
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:
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 ;)