From 63bfbfa5692d779d6851a682c7a683b1c8475291 Mon Sep 17 00:00:00 2001
From: Jason Murray <jason@chaosaffe.io>
Date: Wed, 23 Jan 2019 02:31:26 +0100
Subject: [PATCH] Use kubectl apply instead of create

Resources can be created _and_ updated with `apply` without receiving errors
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 442dd10b..d25e2c1a 100644
--- a/README.md
+++ b/README.md
@@ -71,13 +71,13 @@ This project is intended to be used as a library (i.e. the intent is not for you
 Though for a quickstart a compiled version of the Kubernetes [manifests](manifests) generated with this library (specifically with `example.jsonnet`) is checked into this repository in order to try the content out quickly. To try out the stack un-customized run:
  * Simply create the stack:
 ```
-$ kubectl create -f manifests/ || true
+$ kubectl apply -f manifests/ || true
 
 # It can take a few seconds for the above 'create manifests' command to fully create the following resources, so verify the resources are ready before proceeding.
 until kubectl get customresourcedefinitions servicemonitors.monitoring.coreos.com ; do date; sleep 1; echo ""; done
 until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done
 
-$ kubectl create -f manifests/ 2>/dev/null || true  # This command sometimes may need to be done twice (to workaround a race condition).
+$ kubectl apply -f manifests/ 2>/dev/null || true  # This command sometimes may need to be done twice (to workaround a race condition).
 ```
  * And to teardown the stack:
 ```
-- 
GitLab