Skip to content

Wiping option for MongoDB resources during clusters ingestion (KHaaS only)#364

Merged
jt-dd merged 1 commit intomainfrom
jt-dd/wiping-storedb-data-config
Nov 13, 2025
Merged

Wiping option for MongoDB resources during clusters ingestion (KHaaS only)#364
jt-dd merged 1 commit intomainfrom
jt-dd/wiping-storedb-data-config

Conversation

@jt-dd
Copy link
Copy Markdown
Contributor

@jt-dd jt-dd commented Nov 13, 2025

To avoid indefinitely adding new resources to the MongoDB database, adding an option to wipe previous entry during ingestion. This mechanism is only for KubeHound As a Service (KHaaS). This needs to be set in the kubehound config file:

# Store database configuration
mongodb:
  # Connection URL to the mongo DB instance
  url: "mongodb://localhost:27017"

  # Timeout on requests to the mongo DB instance
  connection_timeout: 30s
  
  # Wipe old copy of k8s/kubehound resources in mongodb
  wipe: true

Note: For now this is not the default behavior.

@jt-dd jt-dd marked this pull request as ready for review November 13, 2025 17:20
@jt-dd jt-dd requested a review from a team as a code owner November 13, 2025 17:20
@jt-dd jt-dd merged commit a96f534 into main Nov 13, 2025
9 checks passed
@jt-dd jt-dd deleted the jt-dd/wiping-storedb-data-config branch November 13, 2025 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants