Add 38.0

CHANGELOG.md

@@ -4,6 +4,45 @@ This document summarizes main and fixes changes published in stable (aka `main`)
 
 https://github.com/kubeshark/kubeshark/wiki/CHANGELOG
 
+## 38.0
+
+- The [kubeshark/kubeshark](https://hub.docker.com/r/kubeshark/kubeshark/tags) Docker image splitted into 3 different images to achieve
+faster pulls and ease of maintenance:
+  - [kubeshark/front](https://hub.docker.com/r/kubeshark/front/tags)
+  - [kubeshark/hub](https://hub.docker.com/r/kubeshark/hub/tags)
+  - [kubeshark/worker](https://hub.docker.com/r/kubeshark/worker/tags)
+- The images were version locked to a specific tag, instead now CLI pulls the `latest` tag of all the 3 images above by default.
+The tag of all images can be changed by setting `--docker-tag` option of `tap` command.
+- Similar to Docker tag, the Docker registry can be changed by setting `--docker-registry` option of `tap` command now.
+- The fields of Kubeshark's `config.yaml` and the CLI options are drastically changed to follow a certain convention and
+to comply with the new architecture of Docker images. See the outputs of `kubeshark tap --help` and `kubeshark config` commands.
+- The names of API server and tapper pods are changed to `kubeshark-hub` and `kubeshark-worker` respectively.
+- A new pod named `kubeshark-front` is introduced that serves the React app (web UI).
+- Kubeshark now proxies two ports instead of one. `8899` for the React app, NGINX server (`kubeshark-front` pod) and `8898` for the Hub, Go Gin server.
+- The RESTful API provided by Hub is drastically different than the old API server.
+- When you apply a filter, the `q` query parameter is set to your filter in the front-end. Similarly, if the `q` query parameter is present, Kubeshark uses that value as the filter.
+- Migrated from Basenine database server to a PCAP-based distributed storage for storing the traffic. The encrypted/TLS traffic is also converted to a
+regular TCP stream and stored as a PCAP file. We're storing raw packets for unencrypted TCP connections. Workers store the each TCP stream in a separate PCAP file. A PCAP file
+can contain one or more items.
+- A button with "Diskette icon" added to left-pane to download/export a merged PCAP snapshot that matching your filter.
+- Exported/download PCAP snapshots can be viewed using `kubeshark tap --pcap <TAR_GZ_PATH>` command.
+- A new section added to right-pane that contains various information like Node IP, port, Worker IP, port, TCP stream ID and item index.
+This section enables you to download the individual PCAP file of the TCP streams and see the dissected JSON structure of each index.
+- The replay functionality is re-engineered to replay the payloads of all client packets to the destination host and port by establishing a brand new
+TCP connection. The older version was not really replaying the packets but rather working based on the dissection result and using `net/http` while
+the new version is not HTTP specific. Also it allows you to replay N number of times and lets you set the packet delay.
+- The experimental feature OAS generator (Service Catalog) is removed.
+- The experimental feature Traffic Stats is removed.
+- The items on the left-pane are now updated with 500 milliseconds tick rate.
+- The Service Map is now automatically updated with 500 milliseconds tick rate. The refresh and restart buttons are removed.
+- Kubeshark's UI starts with `timestamp >= now()` filter by default to prevent throttling.
+- The filtering starts from the very beginning, it's like a scan of all the captured traffic. In the old versions
+you had to do infinite scroll to up direction for fetching the results.
+- We have now a better logging system in CLI program and Hub and Worker pods.
+- `UTC.now()` is displayed under the left-pane.
+- The version check against updates of CLI can be now disabled by setting `KUBESHARK_DISABLE_VERSION_CHECK` environment variable to a non-empty value.
+
+
 ## 37.0
 ### changes
 - Mizu is now Kubeshark