Changed kubectl apply -f to kubectl create -f. kubectl apply command leads to conflicts and race conditions. kubectl create works the first time you run it
This commit is contained in:
@@ -71,7 +71,7 @@ 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:
|
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:
|
* Simply create the stack:
|
||||||
```
|
```
|
||||||
$ kubectl apply -f manifests/
|
$ kubectl create -f manifests/
|
||||||
|
|
||||||
# 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.
|
# 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 customresourcedefinitions servicemonitors.monitoring.coreos.com ; do date; sleep 1; echo ""; done
|
||||||
|
Reference in New Issue
Block a user