Creating and Verifying the Couchbase Master Replication Controller

``` This configuration file creates a couchbase-master-rc Replication Controller. This RC has one replica of the pod created using the arungupta/couchbase:k8s image. This image is created using the Dockerfile [here](http://github.com/arun-gupta/couchbase-kubernetes/blob/master/cluster/Dockerfile). This Dockerfile uses a [configuration script](https://github.com/arun-gupta/couchbase-kubernetes/blob/master/cluster/configure-node.sh) to configure the base Couchbase Docker image. First, it uses [Couchbase REST API](http://developer.couchbase.com/documentation/server/current/rest-api/rest-endpoints-all.html) to setup memory quota, setup index, data and query services, security credentials, and loads a sample data bucket. Then, it invokes the appropriate [Couchbase CLI](http://developer.couchbase.com/documentation/server/current/cli/cbcli-intro.html) commands to add the Couchbase node to the cluster or add the node and rebalance the cluster. This is based upon three environment variables: - TYPE: Defines whether the joining pod is worker or master - AUTO\_REBALANCE: Defines whether the cluster needs to be rebalanced - COUCHBASE\_MASTER: Name of the master service For this first configuration file, the TYPE environment variable is set to MASTER and so no additional configuration is done on the Couchbase image. Let’s create and verify the artifacts. Create Couchbase master RC: ``` kubectl create -f cluster-master.yml replicationcontroller "couchbase-master-rc" created service "couchbase-master-service" created ``` List all the services: ``` kubectl get svc NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE couchbase-master-service 10.0.57.201 8091/TCP 30s kubernetes 10.0.0.1 \<none\> 443/TCP 5h ``` Output shows that couchbase-master-service is created. Get all the pods: ``` kubectl get po NAME READY STATUS RESTARTS AGE couchbase-master-rc-97mu5 1/1 Running 0 1m ``` A pod is created using the Docker image specified in the configuration file. Check the RC: ``` kubectl get rc NAME DESIRED CURRENT AGE couchbase-master-rc 1 1 1m ``` It shows that the desired and current number of pods in the RC are matching. Describe the service: ``` kubectl describe svc couchbase-master-service Name: couchbase-master-service Namespace: default Labels: app=couchbase-master-service Selector: app=couchbase-master-pod Type: LoadBalancer IP: 10.0.57.201 LoadBalancer Ingress: a94f1f286590c11e68e100283628cd6c-1110696566.us-west-2.elb.amazonaws.com Port: \<unset\> 8091/TCP NodePort: \<unset\> 30019/TCP Endpoints: 10.244.2.3:8091 Session Affinity: None Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 2m 2m 1 {service-controller } Normal CreatingLoadBalancer Creating load balancer 2m 2m 1 {service-controller } Normal CreatedLoadBalancer Created load balancer ``` Among other details, the address shown next to LoadBalancer Ingress is relevant for us. This address is used to access the Couchbase Web Console. Wait for ~3 mins for the load balancer to be ready to receive requests. Couchbase Web Console is accessible at \<ip\>:8091 and looks like: ![](https://lh5.googleusercontent.com/LFD6JM9zdP7iriH501VipG06GYEs98aEnWJABvxkZZBZeNJpmXXd2FZFQ9C8nn8gOySQoyrzsgR0c021EGmGWobkgFEgSuYt4lfp6lLooYaX4WhisFPHF_7qqUK4TQKhS9w0G0vb)

This section details the process of creating and verifying the Couchbase master Replication Controller (RC) and associated service in Kubernetes. It explains how the RC is created using a configuration file and a Docker image that configures the Couchbase instance. It then provides commands to create the RC and service using 'kubectl', and verify their creation by listing services, pods, and the RC itself. The section further describes how to access the Couchbase Web Console using the LoadBalancer Ingress address obtained from describing the service.