Now Netchecker server is able to work with either of the following storage backends:
etcd
k8s TPR
TPR becomes deprecated in Kubernetes (CRD is the substitution for TPR) and will not be supported in Netchecker in future.
etcd becomes the default persistent storage for Netchecker.
This implementation uses etcd feature of setting TTL for data that is being stored. So that outdated data will be deleted automatically and Netchecker application will always have only relevant agents data in the storage. This way, determining of agent report obsolescence is simply a check of presence of the data for particular agent in the storage. etcd is now responsible for ensuring correct timing (i.e., removing outdated data according to TTL) and RAFT (which is in use in etcd) helps here if case of nodes dates difference.
Now Netchecker server is able to work with either of the following storage backends:
TPR becomes deprecated in Kubernetes (CRD is the substitution for TPR) and will not be supported in Netchecker in future. etcd becomes the default persistent storage for Netchecker. This implementation uses etcd feature of setting TTL for data that is being stored. So that outdated data will be deleted automatically and Netchecker application will always have only relevant agents data in the storage. This way, determining of agent report obsolescence is simply a check of presence of the data for particular agent in the storage. etcd is now responsible for ensuring correct timing (i.e., removing outdated data according to TTL) and RAFT (which is in use in etcd) helps here if case of nodes dates difference.
Closes: https://github.com/Mirantis/k8s-netchecker-server/issues/80