Skip to content

Commit 151c293

Browse files
committed
Fix deployment command.
Fixes #10
1 parent 295a077 commit 151c293

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ $ cd k8s
129129
Now we can use kubectl to generate the basic YAML we need:
130130

131131
```
132-
$ kubectl create deployment gs-spring-boot-k8s --image spring-k8s/gs-spring-boot-k8s:snapshot -o yaml --dry-run=client > deployment.yaml
132+
$ kubectl create deployment gs-spring-boot-k8s --image spring-k8s/spring-k8s/hello-spring-k8s:latest -o yaml --dry-run=client > deployment.yaml
133133
```
134134

135135
Because the image we are using is local, we need to change the https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy[`imagePullPolicy`] for the container in our deployment.
@@ -461,4 +461,4 @@ Getting a Spring Boot application running on Kubernetes requires nothing more th
461461
of Spring Boot has always been to make building and running Java applications as easy as possible, and we try to enable
462462
that, no matter how you choose to run your application. Building cloud-native applications with Kubernetes involves
463463
nothing more than creating an image that uses Spring Boot’s built-in image builder and taking advantage of the capabilities
464-
of the Kubernetes platform.
464+
of the Kubernetes platform.

0 commit comments

Comments
 (0)