As the backup feature is introduced, the flow of the SIA has been modified and it fails to repeat its IdentityProvisioning when identity has not been successfully prepared as the following diagram with red square. (This did not happen is SIA v2.1.0) This bug let the init container shut down when instance certificate is not yet prepared.
~Also found out it would be better to have the new BACKUP_MODE (the green square below) that reads instance certificate that is 3rd party generated.~
Decided not to have the backup mode, as BACKUP_MODE is only for k8s, not for others.
Also requires to implement reading instance certificate from local file, with the new implementation as following:
The following diagram is the identitydProvisioning() flow for your information.
TODOs
[x] Fix the flow
[x] Double check logs as the logs might have to be fixed
mlajkim
commented
10 months ago
Background
As the backup feature is introduced, the flow of the SIA has been modified and it fails to repeat its
IdentityProvisioningwhen identity has not been successfully prepared as the following diagram with red square. (This did not happen is SIA v2.1.0) This bug let the init container shut down when instance certificate is not yet prepared.~Also found out it would be better to have the new
BACKUP_MODE(the green square below) that reads instance certificate that is 3rd party generated.~ Decided not to have the backup mode, as BACKUP_MODE is only for k8s, not for others.Also requires to implement reading instance certificate from local file, with the new implementation as following:
The following diagram is the
identitydProvisioning()flow for your information.TODOs
file~athenz.env