Add link to diagram of kubectl rolling-update
				
					
				
			fixes issue: #kubernetes/kubernetes.github.io#528
This commit is contained in:
		@@ -49,7 +49,10 @@ var (
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
		Replaces the specified replication controller with a new replication controller by updating one pod at a time to use the
 | 
							Replaces the specified replication controller with a new replication controller by updating one pod at a time to use the
 | 
				
			||||||
		new PodTemplate. The new-controller.json must specify the same namespace as the
 | 
							new PodTemplate. The new-controller.json must specify the same namespace as the
 | 
				
			||||||
		existing replication controller and overwrite at least one (common) label in its replicaSelector.`)
 | 
							existing replication controller and overwrite at least one (common) label in its replicaSelector.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
							
 | 
				
			||||||
 | 
					`)
 | 
				
			||||||
	rollingUpdate_example = dedent.Dedent(`
 | 
						rollingUpdate_example = dedent.Dedent(`
 | 
				
			||||||
		# Update pods of frontend-v1 using new replication controller data in frontend-v2.json.
 | 
							# Update pods of frontend-v1 using new replication controller data in frontend-v2.json.
 | 
				
			||||||
		kubectl rolling-update frontend-v1 -f frontend-v2.json
 | 
							kubectl rolling-update frontend-v1 -f frontend-v2.json
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user