0

After upgrading spring-cloud-dataflow skipper from

springcloud/spring-cloud-skipper-server:2.4.1.RELEASE

to

bitnami/spring-cloud-skipper:2.8.3-debian-10-r4

I see that my previously DEPLOYED streams are not recognized by skipper and show the UNDEPLOYED status in the server ui. Although the apps remained deployed in the kubernetes cluster. Now I wounder if the data structure changed that skipper uses to store its information about deployments? Since my upgrade is a rather huge jump and also the helm chart changed from springcloud to bitnami I wonder where to find a changelog for the skipper?

dhpizza
  • 361
  • 1
  • 2
  • 10
  • Dumb question, but you ensured the MySQL/MariaDB instance is the same? Worse case scenario you can delete the deployments with kubectl and redeploy. – fiidim Apr 29 '22 at 13:25
  • @fidim yes, valid question :) I have postgresql as RDBMS which is the same. I suspect that the new skipper version brings some schema changes with it - I just dont know how to verify that assumption – dhpizza Apr 29 '22 at 14:34

0 Answers0