7.9. Wait for the replication controller to bring all 4 pods up: apiVersion: v1 kind: ReplicationController metadata: name: my-nginx spec: replicas: 4 template: metadata: labels: TCP name: http selector: k8s-app: nginx-service --- apiVersion: v1 kind: ReplicationController metadata: ©Rancher Labs 2017. All rights Reserved. 49 DEPLOYING AND SCALING KUBERNETES the replication controller is also created in the elk namespace. apiVersion: v1 kind: ReplicationController metadata: name: es namespace: elk labels: component: elasticsearch ©Rancher

com/cilium/cilium/v1.6/ex serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost" ission-controllers/#serviceaccount] or can be directly specified in the Pod, Deployment, ReplicationController resource like this: apiVersion: v1 kind: Pod metadata: name: my-pod spec: serviceAccountName:

com/cilium/cilium/v1.7/ex serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost" ission-controllers/#serviceaccount] or can be directly specified in the Pod, Deployment, ReplicationController resource like this: apiVersion: v1 kind: Pod metadata: name: my-pod spec: serviceAccountName:

com/cilium/cilium/v1.8/ex serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost" ission-controllers/#serviceaccount] or can be directly specified in the Pod, Deployment, ReplicationController resource like this: apiVersion: v1 kind: Pod metadata: name: my-pod spec: serviceAccountName:

com/cilium/cilium/v1.10/e serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost" ission-controllers/#serviceaccount] or can be directly specified in the Pod, Deployment, ReplicationController resource like this: apiVersion: v1 kind: Pod metadata: name: my-pod spec: serviceAccountName:

com/cilium/cilium/v1.9/ex serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost" ission-controllers/#serviceaccount] or can be directly specified in the Pod, Deployment, ReplicationController resource like this: apiVersion: v1 kind: Pod metadata: name: my-pod spec: serviceAccountName:

com/cilium/cilium/v1.11/e serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost" ission-controllers/#serviceaccount] or can be directly specified in the Pod, Deployment, ReplicationController resource like this: apiVersion: v1 kind: Pod metadata: name: my-pod spec: serviceAccountName:

com/cilium/cilium/v1.5/ex serviceaccount "elasticsearch" created service "elasticsearch" created replicationcontroller "es" created role "elasticsearch" created rolebinding "elasticsearch" created pod "outpost"