deep-stack/kompose
7
0
Fork 0
forked from LaconicNetwork/kompose
Code Pull Requests Activity

Adds clarification on commands

Browse Source 
Re-adds '$' to commands
This commit is contained in:
Charlie Drage 2017-07-19 13:06:12 -04:00
parent 796313f626
commit 8e70d89ff7
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -11,7 +11,7 @@
Convert [`docker-compose.yaml`](https://raw.githubusercontent.com/kubernetes/kompose/master/examples/docker-compose.yaml) into Kubernetes deployments and services with one simple command: Convert [`docker-compose.yaml`](https://raw.githubusercontent.com/kubernetes/kompose/master/examples/docker-compose.yaml) into Kubernetes deployments and services with one simple command:
```sh ```sh
kompose convert -f docker-compose.yaml $ kompose convert -f docker-compose.yaml
INFO Kubernetes file "frontend-service.yaml" created INFO Kubernetes file "frontend-service.yaml" created
INFO Kubernetes file "redis-master-service.yaml" created INFO Kubernetes file "redis-master-service.yaml" created
INFO Kubernetes file "redis-slave-service.yaml" created INFO Kubernetes file "redis-slave-service.yaml" created

12
docs/quickstart.md
View File

@ -36,7 +36,7 @@ services:
__2. Run `kompose up` in the same directory__ __2. Run `kompose up` in the same directory__
```bash ```bash
kompose up $ kompose up
We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application. We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application.
If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead. If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead.
@ -53,7 +53,7 @@ __Alternatively, you can run `kompose convert` and deploy with `kubectl`__
__2.1. Run `kompose convert` in the same directory__ __2.1. Run `kompose convert` in the same directory__
```bash ```bash
kompose convert $ kompose convert
INFO Kubernetes file "frontend-service.yaml" created INFO Kubernetes file "frontend-service.yaml" created
INFO Kubernetes file "redis-master-service.yaml" created INFO Kubernetes file "redis-master-service.yaml" created
INFO Kubernetes file "redis-slave-service.yaml" created INFO Kubernetes file "redis-slave-service.yaml" created
@ -65,7 +65,7 @@ INFO Kubernetes file "redis-slave-deployment.yaml" created
__2.2. And start it on Kubernetes!__ __2.2. And start it on Kubernetes!__
```bash ```bash
kubectl create -f frontend-service.yaml,redis-master-service.yaml,redis-slave-service.yaml,frontend-deployment.yaml,redis-master-deployment.yaml,redis-slave-deployment.yaml $ kubectl create -f frontend-service.yaml,redis-master-service.yaml,redis-slave-service.yaml,frontend-deployment.yaml,redis-master-deployment.yaml,redis-slave-deployment.yaml
service "frontend" created service "frontend" created
service "redis-master" created service "redis-master" created
service "redis-slave" created service "redis-slave" created
@ -81,13 +81,13 @@ Now that your service has been deployed, let's access it.
If you're already using `minikube` for your development process: If you're already using `minikube` for your development process:
```bash ```bash
minikube service frontend $ minikube service frontend
``` ```
Otherwise, let's look up what IP your service is using! Otherwise, let's look up what IP your service is using!
```sh ```sh
kubectl describe svc frontend $ kubectl describe svc frontend
Name: frontend Name: frontend
Namespace: default Namespace: default
Labels: service=frontend Labels: service=frontend
@ -106,5 +106,5 @@ No events.
If you're using a cloud provider, your IP will be listed next to `LoadBalancer Ingress`. If you're using a cloud provider, your IP will be listed next to `LoadBalancer Ingress`.
```sh ```sh
curl http://123.45.67.89 $ curl http://123.45.67.89
``` ```