On behalf of the team, I am pleased to announce 1.0.0.M2 releases of Spring Cloud Data Flow for Apache Mesos and Spring Cloud Data Flow for Kubernetes.

Spring Cloud Data Flow for Apache Mesos allows one to use all the goodness of Spring Cloud Data Flow (like the Shell, UI and Flo) while targeting Apache Mesos as a backend. Stream components are deployed as individual apps using Marathon, leveraging the power of the platform to handle scaling and health monitoring.

This second milestone

• Builds upon 1.0.0.M1 release of the Spring Cloud Deployer Mesos/Marathon implementation
• Builds upon 1.0.0.M3 release of Spring Cloud Data Flow
• Replaces spring-cloud-marathon-connector with environment variables for service connection parameters. We will improve the service discovery in future release and tie in to Mesos/Marathon’s native service discovery mechanism for runtime credentials
• Adds support to resolve, register, and run OOTB and custom apps as docker images

For a complete list of changes and improvements, please refer to Spring Cloud Data Flow for Apache Mesos 1.0.0.M2 release

Spring Cloud Data Flow forKubernetes allows one to use all the goodness of Spring Cloud Data Flow (like the Shell, UI and Flo) while targeting Kubernetes as a backend. Stream components are deployed as individual apps using Kubernetes, leveraging the power of the platform to handle scaling and health monitoring.

This second milestone

• Builds upon 1.0.0.M1 release of Spring Cloud Deployer Kubernetes implementation
• Builds upon 1.0.0.M3 release of Spring Cloud Data Flow
• Replaces spring-cloud-kubernetes-connector with environment variables for service connection parameters. We will improve the service discovery in future release and use Kubernetes’ native service discovery mechanism for runtime credentials
• Adds support to resolve, register, and run OOTB and custom apps as docker images

For a complete list of changes and improvements, please refer to Spring Cloud Data Flow Kubernetes 1.0.0.M2 release