Added a note "dcmanager kube-rootca-update and kube-upgrade strategy abort" do not abort (r8, dsr8)
Change-Id: Id6f01faf37a9a2ff41cbf35ca223901b971d5a0d
Signed-off-by: Juanita Balaraj <juanita.balaraj@windriver.com>
(cherry picked from commit 6fa1430857)
			
			
This commit is contained in:
		 Juanita Balaraj
					Juanita Balaraj
				
			
				
					committed by
					
						 Juanita-Balaraj
						Juanita-Balaraj
					
				
			
			
				
	
			
			
			 Juanita-Balaraj
						Juanita-Balaraj
					
				
			
						parent
						
							40e5dd3d4b
						
					
				
				
					commit
					b7fe1afc51
				
			| @@ -5,6 +5,7 @@ Kubernetes Root CA Certificate Update for Distributed Cloud Orchestration | ||||
| ========================================================================= | ||||
|  | ||||
| .. warning:: | ||||
|  | ||||
|     During the Kubernetes Root |CA| update, ``deployments``, ``daemonsets``, and | ||||
|     ``statefulsets`` present in the cluster are rolling restarted. This impacts | ||||
|     services provided by the application. It is highly recommended to schedule | ||||
| @@ -15,13 +16,19 @@ Kubernetes Root |CA| certificate(s) for one or more subclouds in a Distributed | ||||
| Cloud Environment. | ||||
|  | ||||
| The Kubernetes Root |CA| update Distributed Cloud Orchestration commands for | ||||
| DCManager use the keyword ``kube-rootca-update-strategy`` and provide the same | ||||
| DCManager uses the keyword ``kube-rootca-update-strategy`` and provides the same | ||||
| five subcommands as the other orchestrations: :command:`create, delete, apply, | ||||
| abort, show`. | ||||
| abort, and show` commands. | ||||
|  | ||||
| .. note:: | ||||
|  | ||||
|     The DCmanager :command:`kube-rootca-update-strategy abort` command | ||||
|     completes the current updating stage before aborting, to prevent hosts from | ||||
|     being left in a state requiring manual intervention. | ||||
|  | ||||
| DCManager Kubernetes Root |CA| update orchestration considers a subcloud to be | ||||
| 'out of sync' that needs to be orchestrated based on the ``kube-rootca_sync_status`` | ||||
| field, which is updated based on the presence of alarms in the subcloud | ||||
| field. This is updated based on the presence of alarms in the subcloud | ||||
| related to the Kubernetes Root |CA| certificate expiring soon (or expired) | ||||
| status. | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user