This PR adds persistence to the Network Mapper collected information, so it won't be lost on every restart of the network mapper. It stores the network mapper data in a config map under the same namespace. In order to reset the network mapper data, use the otterize mapper reset.
Added a unit test that verifies the config map data saving mechanism works.
Also tested on an actual EKS cluster manually, by resetting the network mapper and making sure the data was not lost.
[x] This change adds test coverage for new/changed/fixed functionality
Checklist
[x] I have added documentation for new/changed functionality in this PR and in github.com/otterize/docs
Description
This PR adds persistence to the Network Mapper collected information, so it won't be lost on every restart of the network mapper. It stores the network mapper data in a config map under the same namespace. In order to reset the network mapper data, use the
otterize mapper reset.References
https://www.notion.so/otterize/Access-Graph-make-network-mapper-persistent-keep-states-between-restarts-98020fa84bd2443fa49dddcc05a6f11d
Testing
Added a unit test that verifies the config map data saving mechanism works. Also tested on an actual EKS cluster manually, by resetting the network mapper and making sure the data was not lost.
Checklist