In order for the multiple ingestion not to overrun one another, we need to scope the building of the graph for each run_id. All the mongo request have been updated by providing them the run_id and cluster_name.
To test it:
Run the ingestor binary (grpc-server): ./kubehound-ingestor --debug
Run a collector against the first cluster: ./kubehound dump cloud --bucket s3://<yourbucket> --khaas-server "127.0.0.1:9000" --insecure --debug
Change Kubernetes cluster: kubectx
Run the collector against the second cluster: ./kubehound dump cloud --bucket s3://<yourbucket> --khaas-server "127.0.0.1:9000" --insecure --debug
You can query the results from the either cluster: kh.nodes().has("run_id","<run_id>")
Other new features:
Adding a prepare method for the cache to have the ability to reset it.
In order for the multiple ingestion not to overrun one another, we need to scope the building of the graph for each run_id. All the mongo request have been updated by providing them the
run_idandcluster_name.To test it:
./kubehound-ingestor --debug./kubehound dump cloud --bucket s3://<yourbucket> --khaas-server "127.0.0.1:9000" --insecure --debugkubectx./kubehound dump cloud --bucket s3://<yourbucket> --khaas-server "127.0.0.1:9000" --insecure --debugkh.nodes().has("run_id","<run_id>")Other new features: