升级后，Spring-Cloud-Dataflow船长无法识别已部署的流
升级弹簧云的dataflow船长之后 从
springcloud/spring-cloud-skipper-server:2.4.1.RELEASE
我看
bitnami/spring-cloud-skipper:2.8.3-debian-10-r4
，我以前部署的流未被船长识别，并显示了服务器UI中未剥削的状态。 尽管这些应用仍部署在Kubernetes群集中。 现在，如果数据结构更改了船长用来存储其有关部署的信息，我会受伤吗？ 由于我的升级是一个相当巨大的跳跃，而且头盔图表从Springcloud变为Bitnami，我想知道在哪里可以找到船长的变形值？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论