Added Note in API Server Named Certificate

dpateriya · skrthomas · bergerhoffer · commit 4035ddc02eea · 2023-05-01T10:13:44.000-04:00
The Kuberentes API server rollout only occurs during 1st certificate addition, for any later certificate renewal/modification the kube-apiserver do not need a new revision.

Update modules/customize-certificates-api-add-named.adoc

Co-authored-by: Sara Thomas &lt;sarthoma@redhat.com&gt;
diff --git a/modules/customize-certificates-api-add-named.adoc b/modules/customize-certificates-api-add-named.adoc
@@ -113,3 +113,8 @@ kube-apiserver   {product-version}.0     True        False         False      14
 ----
 +
 If `PROGRESSING` is showing `True`, wait a few minutes and try again.
++
+[NOTE]
+====
+A new revision of the Kubernetes API server only rolls out if the API server named certificate is added for the first time. When the API server named certificate is renewed, a new revision of the Kubernetes API server does not roll out because the `kube-apiserver` pods dynamically reload the updated certificate.
+====

Original file line number	Diff line number	Diff line change
`@@ -113,3 +113,8 @@ kube-apiserver {product-version}.0 True False False 14`
`113`	`113`	`----`
`114`	`114`	`+`
`115`	`115`	If `PROGRESSING` is showing `True`, wait a few minutes and try again.
	`116`	`++`
	`117`	`+[NOTE]`
	`118`	`+====`
	`119`	+A new revision of the Kubernetes API server only rolls out if the API server named certificate is added for the first time. When the API server named certificate is renewed, a new revision of the Kubernetes API server does not roll out because the `kube-apiserver` pods dynamically reload the updated certificate.
	`120`	`+====`