You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spring-cloud-task-samples/partitioned-batch-job/README.adoc
+56Lines changed: 56 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,3 +40,59 @@ Currently partitions are launched sequentially. To launch them asynchronously
40
40
41
41
NOTE: We need to close the context since the use of ThreadPoolTaskExecutor leaves a thread active thus the app will not terminate.
42
42
To close the application appropriately, we will need to set `spring.cloud.task.closecontextEnabled`` to true.
43
+
44
+
== Running Partitioned sample on Kubernetes
45
+
The current sample is set up to run the partitioning using the `local` deployer, so to change this sample so that it work with the `kubernetes` deployer.
46
+
47
+
=== Changes to the application in order to partition on Kubernetes
48
+
. Replace the `spring-cloud-deployer-local` dependency with `spring-cloud-deployer-kubernetes` in the pom.xml. For example:
Resource resource = new DockerResource("partitioned-batch-job:3.0.0-SNAPSHOT");
85
+
----
86
+
. Build a docker image using the following command:
87
+
+
88
+
[source,bash]
89
+
----
90
+
./mvnw spring-boot:build-image
91
+
----
92
+
93
+
=== Notes on when launching this application on Kubernetes
94
+
95
+
* Be sure to make sure the application has the proper permissions to launch another pod. For example in Spring Cloud Data Flow be sure to set the `deployment-service-account-name` ot `scdf-sa`.
96
+
* When using Spring Cloud Data Flow be sure to set the `entry-point-style` to `boot`.
0 commit comments