Kube Root ca update orchestration must ignore cert alarms
The 'Expiring' and 'Expired' alarms for the certificate need
to be added to the ignored alarms list when creating an update
strategy for kube rootca update orchestration.
The expiring alarm is often used to indicate that an orchestration
is needed.
The expired alarm is added for completeness, even though there is
no automated recovery from it.
Test Plan:
Tested strategy can be created/applied when expiring alarm reported.
Reviewed: https:/ /review. opendev. org/c/starlingx /nfv/+/ 815295 /opendev. org/starlingx/ nfv/commit/ 849c386e84911af 0ac8d0df815f911 347b39f8d6
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 849c386e84911af 0ac8d0df815f911 347b39f8d6
Author: albailey <email address hidden>
Date: Mon Oct 25 07:50:13 2021 -0500
Kube Root ca update orchestration must ignore cert alarms
The 'Expiring' and 'Expired' alarms for the certificate need
to be added to the ignored alarms list when creating an update
strategy for kube rootca update orchestration.
The expiring alarm is often used to indicate that an orchestration
is needed.
The expired alarm is added for completeness, even though there is
no automated recovery from it.
Test Plan:
Tested strategy can be created/applied when expiring alarm reported.
Closes-Bug: 1948673 7bf9872ba0de13a 8802688929f
Signed-off-by: albailey <email address hidden>
Change-Id: I5348a0011f52db