mirror of
				https://github.com/optim-enterprises-bv/kubernetes.git
				synced 2025-11-03 19:58:17 +00:00 
			
		
		
		
	Update README.md for cassandra/hazelcast examples to use kubectl resize
This commit is contained in:
		@@ -5,7 +5,7 @@ The following document describes the development of a _cloud native_ [Cassandra]
 | 
				
			|||||||
This document also attempts to describe the core components of Kubernetes, _Pods_, _Services_ and _Replication Controllers_.
 | 
					This document also attempts to describe the core components of Kubernetes, _Pods_, _Services_ and _Replication Controllers_.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Prerequisites
 | 
					### Prerequisites
 | 
				
			||||||
This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` and ```kubecfg``` command line tools somewhere in your path.  Please see the [getting started](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides) for installation instructions for your platform.
 | 
					This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path.  Please see the [getting started](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides) for installation instructions for your platform.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### A note for the impatient
 | 
					### A note for the impatient
 | 
				
			||||||
This is a somewhat long tutorial.  If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end.
 | 
					This is a somewhat long tutorial.  If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end.
 | 
				
			||||||
@@ -151,7 +151,7 @@ Now this is actually not that interesting, since we haven't actually done anythi
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
Let's resize our cluster to 2:
 | 
					Let's resize our cluster to 2:
 | 
				
			||||||
```sh
 | 
					```sh
 | 
				
			||||||
$ kubecfg resize cassandra 2
 | 
					$ kubectl resize rc cassandra --replicas=2
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Now if you list the pods in your cluster, you should see two cassandra pods:
 | 
					Now if you list the pods in your cluster, you should see two cassandra pods:
 | 
				
			||||||
@@ -181,7 +181,7 @@ UN  10.244.1.10  41.14 KB   256     100.0%            42617acd-b16e-4ee3-9486-68
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
Now let's resize our cluster to 4 nodes:
 | 
					Now let's resize our cluster to 4 nodes:
 | 
				
			||||||
```sh
 | 
					```sh
 | 
				
			||||||
$ kubecfg resize cassandra 4
 | 
					$ kubectl resize rc cassandra --replicas=4
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Examining the status again:
 | 
					Examining the status again:
 | 
				
			||||||
@@ -212,13 +212,13 @@ kubectl create -f cassandra-service.yaml
 | 
				
			|||||||
kubectl create -f cassandra-controller.yaml
 | 
					kubectl create -f cassandra-controller.yaml
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# scale up to 2 nodes
 | 
					# scale up to 2 nodes
 | 
				
			||||||
kubecfg resize cassandra 2
 | 
					kubectl resize rc cassandra --replicas=2
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# validate the cluster
 | 
					# validate the cluster
 | 
				
			||||||
docker exec <container-id> nodetool status
 | 
					docker exec <container-id> nodetool status
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# scale up to 4 nodes
 | 
					# scale up to 4 nodes
 | 
				
			||||||
kubecfg resize cassandra 4
 | 
					kubectl resize rc cassandra --replicas=4
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Seed Provider Source
 | 
					### Seed Provider Source
 | 
				
			||||||
 
 | 
				
			|||||||
@@ -7,7 +7,7 @@ Any topology changes are communicated and handled by Hazelcast nodes themselves.
 | 
				
			|||||||
This document also attempts to describe the core components of Kubernetes, _Pods_, _Services_ and _Replication Controllers_.
 | 
					This document also attempts to describe the core components of Kubernetes, _Pods_, _Services_ and _Replication Controllers_.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Prerequisites
 | 
					### Prerequisites
 | 
				
			||||||
This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` and ```kubecfg``` command line tools somewhere in your path.  Please see the [getting started](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides) for installation instructions for your platform.
 | 
					This example assumes that you have a Kubernetes cluster installed and running, and that you have installed the ```kubectl``` command line tool somewhere in your path.  Please see the [getting started](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides) for installation instructions for your platform.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### A note for the impatient
 | 
					### A note for the impatient
 | 
				
			||||||
This is a somewhat long tutorial.  If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end.
 | 
					This is a somewhat long tutorial.  If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end.
 | 
				
			||||||
@@ -142,7 +142,7 @@ Now this is actually not that interesting, since we haven't actually done anythi
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
Let's resize our cluster to 2:
 | 
					Let's resize our cluster to 2:
 | 
				
			||||||
```sh
 | 
					```sh
 | 
				
			||||||
$ kubecfg resize hazelcast 2
 | 
					$ kubectl resize rc hazelcast --replicas=2
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Now if you list the pods in your cluster, you should see two hazelcast pods:
 | 
					Now if you list the pods in your cluster, you should see two hazelcast pods:
 | 
				
			||||||
@@ -180,7 +180,7 @@ $ kubectl log 16b2beab-94a1-11e4-8a8b-42010af0e23e hazelcast
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
Now let's resize our cluster to 4 nodes:
 | 
					Now let's resize our cluster to 4 nodes:
 | 
				
			||||||
```sh
 | 
					```sh
 | 
				
			||||||
$ kubecfg resize hazelcast 4
 | 
					$ kubectl resize rc hazelcast --replicas=4
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Examine the status again by checking a node’s log and you should see the 4 members connected.
 | 
					Examine the status again by checking a node’s log and you should see the 4 members connected.
 | 
				
			||||||
@@ -199,13 +199,13 @@ kubectl create -f hazelcast-service.yaml
 | 
				
			|||||||
kubectl create -f hazelcast-controller.yaml
 | 
					kubectl create -f hazelcast-controller.yaml
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# scale up to 2 nodes
 | 
					# scale up to 2 nodes
 | 
				
			||||||
kubecfg resize hazelcast 2
 | 
					kubectl resize rc hazelcast --replicas=2
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# validate the cluster
 | 
					# validate the cluster
 | 
				
			||||||
docker exec <container-id> nodetool status
 | 
					docker exec <container-id> nodetool status
 | 
				
			||||||
 | 
					
 | 
				
			||||||
# scale up to 4 nodes
 | 
					# scale up to 4 nodes
 | 
				
			||||||
kubecfg resize hazelcast 4
 | 
					kubectl resize rc hazelcast --replicas=4
 | 
				
			||||||
```
 | 
					```
 | 
				
			||||||
 | 
					
 | 
				
			||||||
### Hazelcast Discovery Source
 | 
					### Hazelcast Discovery Source
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user