starlingx
/
stx-puppet
Code Issues Proposed changes

Restart sysinv API after k8s root CA update 

During k8s root CA certificate update, the certificates in admin.conf
have been updated. Since both sysinv conductor and api cache k8s client
that get credentials from admin.conf, both of they need to restart.
(currently only conductor is restarted)

Closes-Bug: 1943080
Signed-off-by: Andy Ning <andy.ning@windriver.com>
Change-Id: Ic92d6e95980b088108b175d0cafa905fda2ffb09
This commit is contained in:
Andy Ning 2021-09-09 10:00:42 -04:00
parent 6b64fc782a
commit d44a8080cf
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
puppet-manifests/src/modules/platform/manifests/kubernetes.pp
View File

@ -943,9 +943,10 @@ class platform::kubernetes::master::rootca::trustnewca::runtime
environment => [ 'KUBECONFIG=/etc/kubernetes/admin.conf' ],
command => "kubectl config set-cluster kubernetes --certificate-authority ${rootca_certfile} --embed-certs",
}
# Restart sysinv-conductor since it uses admin.conf
# Restart sysinv-conductor and sysinv-inv since they cache clients with
# credentials from admin.conf
-> exec { 'restart_sysinv_conductor':
command => 'sm-restart-safe service sysinv-conductor',
command => 'sm-restart service sysinv-conductor',
}
# Restart cert-mon since it uses admin.conf
-> exec { 'restart_cert_mon':