-
Notifications
You must be signed in to change notification settings - Fork 583
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
Kubernetes 1.21.x: CronJob API moved from v1beta1 to v1 #5416
Comments
Hi @jankeigen , This is fixed in the upcoming Thanks Closing in favor of spring-cloud/spring-cloud-deployer-kubernetes#529 |
We tried to upgrade the scdf version to solve the above issue, but its not working. I build the latest scdf version 2.11.0 with oracle dependency. I am using oracle db and the application is not able to load data from the custom datasource. Rather it tries to get from default schema. See the error below. 2023-10-05 14:49:50.496 DEBUG 1 --- [nio-8080-exec-9] org.hibernate.SQL : select appregistr0_.id as id1_0_, appregistr0_.object_version as object_version2_0_, appregistr0_.boot_version as boot_version3_0_, appregistr0_.default_version as default_version4_0_, appregistr0_.metadata_uri as metadata_uri5_0_, appregistr0_.name as name6_0_, appregistr0_.type as type7_0_, appregistr0_.uri as uri8_0_, appregistr0_.version as version9_0_ from app_registration appregistr0_ where appregistr0_.default_version=1 order by appregistr0_.name asc fetch first ? rows only 2023-10-05 14:49:50.527 DEBUG 1 --- [nio-8080-exec-9] o.h.engine.jdbc.spi.SqlExceptionHelper : could not extract ResultSet [n/a] |
HI @sampathsri thanks for the report. We will prioritize looking into this. Let's track this under the other ticket you created #5497 |
One update on this story for someone facing this after migrating it to 2.11 in kubernetes 1.26X version . After migrating it to SCDF 2.11, the schedules page in SCDF displays the data by interacting wit openshift cron jobs api. But it wont allow you to create schedule from scdf. For this to work, we need to update the kubernetes-client to latest version . In my case, i updated it to |
Thanks for the follow up @sampathsri . I created a new issue based on your feedback. We will investigate. |
Description:
On Kubernetes 1.21.x or OpenShift 4.12 the CronJob API moved from v1beta1 to v1. This results in an HTTP 404 when selecting the "Schedules" menu item.
Failure executing: GET at: https://172.30.0.1/apis/batch/v1beta1/namespaces/my-namespace/cronjobs. Message: the server could not find the requested resource. Received status: Status(apiVersion=v1, code=404, details=StatusDetails(causes=[], group=null, kind=null, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=the server could not find the requested resource, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=NotFound, status=Failure, additionalProperties={}).
Release versions:
2.10.3
Steps to reproduce:
Install SCDF on Kubernetes 1.21.x or OpenShift 4.12 and select the "Schedules" menu item.
Screenshots:
The text was updated successfully, but these errors were encountered: