It looks like the SCC container is saving all the configuraitons (certs, logging accounts, subaccount and path settings etc...) all in the container RW layer.
with this, if the container restart or get currupted, then seems all those configuraiton are lost.
I know there is a native backup function existing in SCC webui, but it is not convenience:
always forget to backup the latest configuration manually;
if the container getting restarted automatically (in K8S), then it needs some people manually login and restore the configure.
Question:
as the SCC runtime files and configure files are both in the same parent folder, how can people persistent the confiuration to a separated folder (pvc)?
and, if I upgrade the SCC version by rebuild a new container, how to make sure the configure files are automatically there?
It looks like the SCC container is saving all the configuraitons (certs, logging accounts, subaccount and path settings etc...) all in the container RW layer. with this, if the container restart or get currupted, then seems all those configuraiton are lost.
I know there is a native backup function existing in SCC webui, but it is not convenience:
Question: as the SCC runtime files and configure files are both in the same parent folder, how can people persistent the confiuration to a separated folder (pvc)? and, if I upgrade the SCC version by rebuild a new container, how to make sure the configure files are automatically there?