On behalf of the team, I am pleased to announce the release of the first milestone of Spring Cloud Data Flow for Kubernetes 1.1 along with a 1.0.1 maintenance release.
Spring Cloud Data Flow for Kubernetes provides support for orchestrating long-running (streaming) and short-lived (task/batch) data microservices on Kubernetes.
Note: A great way to start using the new release(s) is to follow the release matrix on the project page, which includes the download coordinates and the links to the reference guide.
The most significant change for both of these releases is the way we handle task launching. We used to orchestrate them as a Job with associated Pods, but that proved problematic in terms of failed jobs getting restarted even with a RestartPolicy specified as “Never”. To resolve this, we now launch the tasks using bare pods and we also give each launched task and corresponding pod a unique id.
The 1.1.0.M1 release builds on the recent 1.1 M1 release of the core Spring Cloud Data Flow project.
The 1.0.1.RELEASE maintenance release builds on the latest 1.0.1 maintenance release of the core Spring Cloud Data Flow project.
Review the 1.0.1.RELEASE marker and the Spring Cloud Deployer for Kubernetes 1.0.4.RELEASE marker to learn more about the incremental improvements.
Docker images containing the Spring Cloud Data Flow Server for Kubernetes for both of these releases are available from the Docker Hub repo.
To get started using Spring Cloud Data Flow for Kubernetes follow the steps outlined in the reference documentation.