|
|
@@ -16,7 +16,7 @@ with the basic authentication username and password.
|
|
|
|
Here is an example replication controller specification that creates 4 instances of Elasticsearch which is in the file
|
|
|
|
Here is an example replication controller specification that creates 4 instances of Elasticsearch which is in the file
|
|
|
|
[music-rc.yaml](music-rc.yaml).
|
|
|
|
[music-rc.yaml](music-rc.yaml).
|
|
|
|
```
|
|
|
|
```
|
|
|
|
apiVersion: v1beta3
|
|
|
|
apiVersion: v1
|
|
|
|
kind: ReplicationController
|
|
|
|
kind: ReplicationController
|
|
|
|
metadata:
|
|
|
|
metadata:
|
|
|
|
labels:
|
|
|
|
labels:
|
|
|
@@ -68,7 +68,7 @@ for the replication controller (in this case `mytunes`).
|
|
|
|
Before creating pods with the replication controller a secret containing the bearer authentication token
|
|
|
|
Before creating pods with the replication controller a secret containing the bearer authentication token
|
|
|
|
should be set up. A template is provided in the file [apiserver-secret.yaml](apiserver-secret.yaml):
|
|
|
|
should be set up. A template is provided in the file [apiserver-secret.yaml](apiserver-secret.yaml):
|
|
|
|
```
|
|
|
|
```
|
|
|
|
apiVersion: v1beta3
|
|
|
|
apiVersion: v1
|
|
|
|
kind: Secret
|
|
|
|
kind: Secret
|
|
|
|
metadata:
|
|
|
|
metadata:
|
|
|
|
name: apiserver-secret
|
|
|
|
name: apiserver-secret
|
|
|
@@ -92,7 +92,7 @@ eUdsRGNNdlNaUFg0UHlQMFE1YkhnQVlnaTFpeUVIdjIK=
|
|
|
|
```
|
|
|
|
```
|
|
|
|
resulting in the file:
|
|
|
|
resulting in the file:
|
|
|
|
```
|
|
|
|
```
|
|
|
|
apiVersion: v1beta3
|
|
|
|
apiVersion: v1
|
|
|
|
kind: Secret
|
|
|
|
kind: Secret
|
|
|
|
metadata:
|
|
|
|
metadata:
|
|
|
|
name: apiserver-secret
|
|
|
|
name: apiserver-secret
|
|
|
@@ -113,10 +113,10 @@ $ kubectl create -f music-rc.yaml --namespace=mytunes
|
|
|
|
replicationcontrollers/music-db
|
|
|
|
replicationcontrollers/music-db
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
```
|
|
|
|
It's also useful to have a [service](../../docs/services.md) with an external load balancer for accessing the Elasticsearch
|
|
|
|
It's also useful to have a [service](../../docs/services.md) with an load balancer for accessing the Elasticsearch
|
|
|
|
cluster which can be found in the file [music-service.yaml](music-service.yaml).
|
|
|
|
cluster which can be found in the file [music-service.yaml](music-service.yaml).
|
|
|
|
```
|
|
|
|
```
|
|
|
|
apiVersion: v1beta3
|
|
|
|
apiVersion: v1
|
|
|
|
kind: Service
|
|
|
|
kind: Service
|
|
|
|
metadata:
|
|
|
|
metadata:
|
|
|
|
name: music-server
|
|
|
|
name: music-server
|
|
|
@@ -130,7 +130,7 @@ spec:
|
|
|
|
- name: db
|
|
|
|
- name: db
|
|
|
|
port: 9200
|
|
|
|
port: 9200
|
|
|
|
targetPort: es
|
|
|
|
targetPort: es
|
|
|
|
createExternalLoadBalancer: true
|
|
|
|
type: LoadBalancer
|
|
|
|
```
|
|
|
|
```
|
|
|
|
Let's create the service with an external load balancer:
|
|
|
|
Let's create the service with an external load balancer:
|
|
|
|
```
|
|
|
|
```
|
|
|
|