github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-11 06:02:18 +00:00
Code Issues Projects Releases Wiki Activity

Use example syncer tags instead of hard-coded examples in doc

Browse Source
This commit is contained in:
Janet Kuo
2015-07-20 15:46:20 -07:00
parent 2bd53119b1
commit 180798cfa4
22 changed files with 306 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
examples/celery-rabbitmq/README.md
View File

@@ -64,7 +64,7 @@ You should already have turned up a Kubernetes cluster. To get the most of this
The Celery task queue will need to communicate with the RabbitMQ broker. RabbitMQ will eventually appear on a separate pod, but since pods are ephemeral we need a service that can transparently route requests to RabbitMQ.
Use the file [`examples/celery-rabbitmq/rabbitmq-service.yaml`](rabbitmq-service.yaml):
<!-- BEGIN MUNGE: EXAMPLE rabbitmq-service.yaml -->
```yaml
apiVersion: v1
@@ -81,6 +81,9 @@ spec:
component: rabbitmq
```
[Download example](rabbitmq-service.yaml)
<!-- END MUNGE: EXAMPLE -->
To start the service, run:
```sh
@@ -94,6 +97,8 @@ This service allows other pods to connect to the rabbitmq. To them, it will be s
A RabbitMQ broker can be turned up using the file [`examples/celery-rabbitmq/rabbitmq-controller.yaml`](rabbitmq-controller.yaml):
<!-- BEGIN MUNGE: EXAMPLE rabbitmq-controller.yaml -->
```yaml
apiVersion: v1
kind: ReplicationController
@@ -121,6 +126,9 @@ spec:
cpu: 100m
```
[Download example](rabbitmq-controller.yaml)
<!-- END MUNGE: EXAMPLE -->
Running `$ kubectl create -f examples/celery-rabbitmq/rabbitmq-controller.yaml` brings up a replication controller that ensures one pod exists which is running a RabbitMQ instance.
Note that bringing up the pod includes pulling down a docker image, which may take a few moments. This applies to all other pods in this example.
@@ -130,6 +138,8 @@ Note that bringing up the pod includes pulling down a docker image, which may ta
Bringing up the celery worker is done by running `$ kubectl create -f examples/celery-rabbitmq/celery-controller.yaml`, which contains this:
<!-- BEGIN MUNGE: EXAMPLE celery-controller.yaml -->
```yaml
apiVersion: v1
kind: ReplicationController
@@ -157,6 +167,9 @@ spec:
cpu: 100m
```
[Download example](celery-controller.yaml)
<!-- END MUNGE: EXAMPLE -->
There are several things to point out here...
Like the RabbitMQ controller, this controller ensures that there is always a pod is running a Celery worker instance. The celery-app-add Docker image is an extension of the standard Celery image. This is the Dockerfile:
@@ -207,6 +220,8 @@ Flower is a web-based tool for monitoring and administrating Celery clusters. By
First, start the flower service with `$ kubectl create -f examples/celery-rabbitmq/flower-service.yaml`. The service is defined as below:
<!-- BEGIN MUNGE: EXAMPLE flower-service.yaml -->
```yaml
apiVersion: v1
kind: Service
@@ -223,6 +238,9 @@ spec:
type: LoadBalancer
```
[Download example](flower-service.yaml)
<!-- END MUNGE: EXAMPLE -->
It is marked as external (LoadBalanced). However on many platforms you will have to add an explicit firewall rule to open port 5555.
On GCE this can be done with:
@@ -234,6 +252,8 @@ Please remember to delete the rule after you are done with the example (on GCE:
To bring up the pods, run this command `$ kubectl create -f examples/celery-rabbitmq/flower-controller.yaml`. This controller is defined as so:
<!-- BEGIN MUNGE: EXAMPLE flower-controller.yaml -->
```yaml
apiVersion: v1
kind: ReplicationController
@@ -259,6 +279,9 @@ spec:
cpu: 100m
```
[Download example](flower-controller.yaml)
<!-- END MUNGE: EXAMPLE -->
This will bring up a new pod with Flower installed and port 5555 (Flower's default port) exposed through the service endpoint. This image uses the following command to start Flower:
```sh