spring-cloud-dataflow skipper does not recognize deployed streams after upgrade

74 views Asked by At

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?

0

There are 0 answers