From e8470e9d4fd98dadf953e07dca561ecab625bf4f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9my-Christophe=20Schermesser?= Date: Thu, 23 May 2019 14:11:41 +0200 Subject: [PATCH] fix: fix services names (#49) --- 07-deployment/README.md | 2 +- .../{03-simple-service.yml => 03-internal-service.yml} | 2 +- 08-service/04-ingress.yml | 2 +- 08-service/README.md | 10 +++++----- 4 files changed, 8 insertions(+), 8 deletions(-) rename 08-service/{03-simple-service.yml => 03-internal-service.yml} (80%) diff --git a/07-deployment/README.md b/07-deployment/README.md index d3b5eed..104fabc 100644 --- a/07-deployment/README.md +++ b/07-deployment/README.md @@ -137,7 +137,7 @@ Change again the number of replicas to `2`, reapply, see what is happening. We know how to scale up/down a deployment, but how can we deploy a new version of the application. To achieve this, we need to tell Kubernetes to update the image we are using in our `deployment`, for this: ```sh -$ kubectl set image deployment/simple-deployment simple-service=mhausenblas/simpleservice:0.5.0 +$ kubectl set image deployment/simple-deployment simple-pod=mhausenblas/simpleservice:0.5.0 deployment.apps "simple-deployment" image updated ``` diff --git a/08-service/03-simple-service.yml b/08-service/03-internal-service.yml similarity index 80% rename from 08-service/03-simple-service.yml rename to 08-service/03-internal-service.yml index 579aaa6..8ad52a3 100644 --- a/08-service/03-simple-service.yml +++ b/08-service/03-internal-service.yml @@ -2,7 +2,7 @@ apiVersion: v1 kind: Service metadata: - name: simple-service + name: simple-internal-service spec: ports: - port: 80 diff --git a/08-service/04-ingress.yml b/08-service/04-ingress.yml index 99b76a7..371129d 100644 --- a/08-service/04-ingress.yml +++ b/08-service/04-ingress.yml @@ -7,5 +7,5 @@ metadata: nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: backend: - serviceName: simple-service + serviceName: simple-internal-service servicePort: 80 diff --git a/08-service/README.md b/08-service/README.md index 843a265..355c99c 100644 --- a/08-service/README.md +++ b/08-service/README.md @@ -86,22 +86,22 @@ is central to Kubernetes. It is with those fields that you will tell Kubernetes Apply the service: ```sh -$ kubectl apply -f 08-service/03-simple-service.yml +$ kubectl apply -f 08-service/03-simple-internal-service.yml service "simple-service" created ``` Your service is now accessible internally, try this in your `bash` container: ```sh -root@bash:/# nslookup simple-service +root@bash:/# nslookup simple-internal-service Server: 10.96.0.10 Address: 10.96.0.10#53 -Name: simple-service.default.svc.cluster.local +Name: simple-internal-service.default.svc.cluster.local Address: 10.96.31.244 ``` -Try to curl the `/info` url, remember the `ports` we choose in the `service`. +Try to curl the `/healthz` url, remember the `ports` we choose in the `service`. Can you access this service from the outside of Kubernetes? @@ -130,7 +130,7 @@ metadata: nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: backend: - serviceName: simple-service + serviceName: simple-internal-service servicePort: 80 ```