Closed v1bh0r closed 1 year ago
The skipper gets the dependency on deployer from here - https://github.com/spring-cloud/spring-cloud-skipper/blob/main/pom.xml#LL39C1-L40C1 It currently points to 2.8.4 which explains the issue.
https://github.com/spring-cloud/spring-cloud-deployer-kubernetes "2.9.x adds support for k8s 1.25 and drops support for k8s < 1.21"
Can someone recommend any workarounds please?
Hi @v1bh0r ,
This is a duplicate of https://github.com/spring-cloud/spring-cloud-deployer-kubernetes/issues/529.
Unfortunately this is a breaking API change and will only be available in SCDF 2.11.0. See here for more details.
SCDF 2.11.0
has a target date of 2023-06-20.
Name and Version
bitnami/spring-cloud-dataflow 18.1.1
What architecture are you using?
amd64
What steps will reproduce the bug?
We have a spring cloud data flow cluster installed in kubernetes (Server Version: v1.25.5). We installed it using the helm chart bitnami/spring-cloud-dataflow 18.1.1
Following is the deployment manifest for the scdf server:
Following is the output of the command kubectl api-versions
We are getting the following error whenever we try to load the schedules page in the UI.
What do you see instead?
Folks, any help troubleshooting why it is calling batch/v1beta1 instead of batch/v1 is highly appreciated.