From 800eae29f442f30d908e614fc8aa758425d06183 Mon Sep 17 00:00:00 2001
From: Alon Girmonsky <1990761+alongir@users.noreply.github.com>
Date: Thu, 20 Apr 2023 16:53:02 -0700
Subject: [PATCH] Updated CHANGELOG (markdown)

---
 CHANGELOG.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0169415..8fa8573 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,11 +8,12 @@ https://github.com/kubeshark/kubeshark/wiki/CHANGELOG
 
 ### changes
 
- - Removed the `-A` flag. Now Kubeshark targets all namespaces by default. Use `-n` flag to specify namespaces.
- - Changed the `storagelimit` option's format from `200MB` to `200Mi` for complying with Kubernetes' internal quantity parser.
+ - All namespaces are now tapped by default and there's no need to use the `-A` flag. The `-n` flag can be used to specify a certain namespaces.
+ - Starting to use node-level persistent volumes to ensure no data loss. As a result of this change, certain changes follow:
  - Added a `PersistentVolumeClaim` that the worker DaemonSet mounts.
+ - Changed the `storagelimit` option's format from `200MB` to `200Mi` for complying with Kubernetes' internal quantity parser.
  - Added `storageclass` option to set the `StorageClass` in `PersistentVolumeClaim`. Default value is `standard`.
- - Run `kubeshark config -r` to regenerate the `~/.kubeshark/config.yaml`.
+ - The above is a breaking change: You need to run `kubeshark config -r` to regenerate the `~/.kubeshark/config.yaml` incase of an existing configuration file.
 
 ## 38.4