From 77439ab55d90503c53df6f325d057f26fd3105c1 Mon Sep 17 00:00:00 2001 From: Ahmed Sabbour <103856+sabbour@users.noreply.github.com> Date: Tue, 16 Jul 2019 10:56:35 -0700 Subject: [PATCH] Fix yaml --- .dockerignore | 1 - _entries/03-01 appoverview.md | 4 ++-- yaml/{ostoy-fe-deployment.yaml => ostoy-fe.yaml} | 1 - 3 files changed, 2 insertions(+), 4 deletions(-) rename yaml/{ostoy-fe-deployment.yaml => ostoy-fe.yaml} (99%) diff --git a/.dockerignore b/.dockerignore index f83b1b6..e69de29 100644 --- a/.dockerignore +++ b/.dockerignore @@ -1 +0,0 @@ -app/ \ No newline at end of file diff --git a/_entries/03-01 appoverview.md b/_entries/03-01 appoverview.md index d7b4ac9..e240841 100644 --- a/_entries/03-01 appoverview.md +++ b/_entries/03-01 appoverview.md @@ -11,8 +11,8 @@ parent-id: lab-clusterapp - OSToy front-end container image: - OSToy microservice container image: - Deployment Definition YAMLs: - - [ostoy-fe-deployment.yaml](/yaml/ostoy-fe-deployment.yaml) - - [ostoy-microservice-deploymen.yaml](/yaml/ostoy-microservice-deployment.yaml) + - [ostoy-fe.yaml](/yaml/ostoy-fe.yaml) + - [ostoy-microservice-deployment.yaml](/yaml/ostoy-microservice-deployment.yaml) > **Note** In order to simplify the deployment of the app (which you will do next) we have included all the objects needed in the above YAMLs as "all-in-one" YAMLs. In reality though, an enterprise would most likely want to have a different yaml file for each Kubernetes object. diff --git a/yaml/ostoy-fe-deployment.yaml b/yaml/ostoy-fe.yaml similarity index 99% rename from yaml/ostoy-fe-deployment.yaml rename to yaml/ostoy-fe.yaml index 2941446..27b2409 100644 --- a/yaml/ostoy-fe-deployment.yaml +++ b/yaml/ostoy-fe.yaml @@ -1,4 +1,3 @@ ---- apiVersion: v1 kind: PersistentVolumeClaim metadata: