mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-11 06:02:18 +00:00
Make munger begin/end less generic
Just force the beginMungeTag() endMungeTag() macros on users, by hiding it under the covers. It really simplies things for users.
This commit is contained in:
@@ -82,7 +82,7 @@ spec:
|
||||
```
|
||||
|
||||
[Download example](rabbitmq-service.yaml)
|
||||
<!-- END MUNGE: EXAMPLE -->
|
||||
<!-- END MUNGE: EXAMPLE rabbitmq-service.yaml -->
|
||||
|
||||
To start the service, run:
|
||||
|
||||
@@ -127,7 +127,7 @@ spec:
|
||||
```
|
||||
|
||||
[Download example](rabbitmq-controller.yaml)
|
||||
<!-- END MUNGE: EXAMPLE -->
|
||||
<!-- END MUNGE: EXAMPLE rabbitmq-controller.yaml -->
|
||||
|
||||
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.
|
||||
|
||||
@@ -168,7 +168,7 @@ spec:
|
||||
```
|
||||
|
||||
[Download example](celery-controller.yaml)
|
||||
<!-- END MUNGE: EXAMPLE -->
|
||||
<!-- END MUNGE: EXAMPLE celery-controller.yaml -->
|
||||
|
||||
There are several things to point out here...
|
||||
|
||||
@@ -239,7 +239,7 @@ spec:
|
||||
```
|
||||
|
||||
[Download example](flower-service.yaml)
|
||||
<!-- END MUNGE: EXAMPLE -->
|
||||
<!-- END MUNGE: EXAMPLE flower-service.yaml -->
|
||||
|
||||
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:
|
||||
@@ -280,7 +280,7 @@ spec:
|
||||
```
|
||||
|
||||
[Download example](flower-controller.yaml)
|
||||
<!-- END MUNGE: EXAMPLE -->
|
||||
<!-- END MUNGE: EXAMPLE flower-controller.yaml -->
|
||||
|
||||
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:
|
||||
|
||||
|
Reference in New Issue
Block a user