From 151c293fe0df2ddcd8560f5279843d60bfc28933 Mon Sep 17 00:00:00 2001 From: Ryan Baxter Date: Wed, 4 Dec 2024 10:23:29 -0500 Subject: [PATCH] Fix deployment command. Fixes #10 --- README.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.adoc b/README.adoc index 3429a51..6af8e4c 100644 --- a/README.adoc +++ b/README.adoc @@ -129,7 +129,7 @@ $ cd k8s Now we can use kubectl to generate the basic YAML we need: ``` -$ kubectl create deployment gs-spring-boot-k8s --image spring-k8s/gs-spring-boot-k8s:snapshot -o yaml --dry-run=client > deployment.yaml +$ kubectl create deployment gs-spring-boot-k8s --image spring-k8s/spring-k8s/hello-spring-k8s:latest -o yaml --dry-run=client > deployment.yaml ``` 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 of Spring Boot has always been to make building and running Java applications as easy as possible, and we try to enable that, no matter how you choose to run your application. Building cloud-native applications with Kubernetes involves nothing more than creating an image that uses Spring Boot’s built-in image builder and taking advantage of the capabilities -of the Kubernetes platform. \ No newline at end of file +of the Kubernetes platform.