Skip to content

Releases: threatstack/threatstack-helm

3.2.2

19 Jul 16:19
9aad0e7
Compare
Choose a tag to compare

Update for latest agent version.

3.2.1

05 Jun 14:36
Compare
Choose a tag to compare

New release includes PRs #53 and #54

Thanks @jullianow !

3.2.0

23 Jan 16:10
73079dd
Compare
Choose a tag to compare
  • Updated default agent version
  • Included the refactor and fixes from #50 (thanks @jullianow !)
  • Added values to configure the deployments for CRI-O and OpenShift
  • Other fixes and improvements

3.1.1

07 Sep 16:52
2fead5d
Compare
Choose a tag to compare

Updated helm chart for latest agent release version, and incorporated @jullianow 's updates in #44

Thanks Julian!

3.1.0

23 Aug 17:23
8a421b2
Compare
Choose a tag to compare

Update to latest agent version.

  • Added host mount propagation
  • Multiple fixes, including one from the communtity!
  • License and contributing process updates

3.0.1

16 May 16:35
50f6a33
Compare
Choose a tag to compare

Latest version of the Threat Stack Helm Chart, to go with agent 3.0.0. This chart adds:

  • eBPF flags/options
  • Low Power Mode

If you happened to download the 3.0.0 chart for the short time it was available, we’d recommend using 3.0.1.

2.4.0

24 Feb 16:09
31f4f78
Compare
Choose a tag to compare

Introduce automatic redeployment of the Daemonset

  • Added podAnnotations and priorityClassName to the api-reader Deployment, to bring to parity with the Daemonset
  • Updated README.md content with changes.

2.3.0

17 Feb 15:49
4887a63
Compare
Choose a tag to compare

Updated agent version to new release.

2.2.1

10 Nov 15:19
ece4e2e
Compare
Choose a tag to compare

Update chart default to latest agent version (2.4.1)

2.2.0

26 Oct 18:35
9a7b9c4
Compare
Choose a tag to compare

This version is not compatible with agents before 2.4.0.

  • Changed the logic of how the container daemon socket enablement works, as by default in 2.4.0, the agent will attempt to figure out what daemons are running.
    • As a result the enableDocker/enableContainerd flags are not set now. if you do set them to true/false, you will cause the agent to explicitly enable/disable those features
  • Removed unneeded volumeMounts as a result of the previously documented daemon socket change
  • Modified the liveness probe period 60 -> 360