Prepare for v1.3.0 release

Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>

contrib/upgrade-notes/latest.md

@@ -3,7 +3,7 @@
 Read the upgrade notes carefully before upgrading Tetragon.
 Depending on your setup, changes listed here might require a manual intervention.
 
-* Behavior of `export-file-perm` flag (and corresponding Helm value `tetragon.exportFilePerm`) changed. In case the export file exists, but has different permissions than specified in the option, Tetragon will change the file permissions on the next log rotation. In older versions, log rotation preserved permissions of the existing file. Before upgrading check if permissions of the existing export file match the option (600 by default), and set the agent flag or Helm value to the desired value if needed.
+* TBD
 
 ### Agent Options
 
@@ -19,29 +19,8 @@ Depending on your setup, changes listed here might require a manual intervention
 
 ### Events (protobuf API)
 
-
-#### New events for `syscall64` type
-
-Previous versions of Tetragon did not distinguish between different ABIs when using the syscall64 type
-because the output was just a `size_arg` with the id. When executing the `getcpu` syscall, for example, the JSON
-for 64- and 32-bits would be:
-```
-"args":[{"size_arg":"309"}]
-"args":[{"size_arg":"318"}]
-```
-
-Note that id 318 for `x86_64` is a different syscall: `getrandom` so we cannot distinguish between a `getrandom` syscall on x86_64
-and a `getcpu` call on 32-bit (`i386`). To address this issue, the output of `syscall64` was changed to a `SyscallId` object that
-also includes the ABI. So the JSON for 64- and 32-bits `getcpu` now is:
-
-```
-"args":[{"syscall_id":{"id":309,"abi":"x64"}}]
-"args":[{"syscall_id":{"id":318,"abi":"i386"}}]
-```
-
-Users that want to maintain the old behavior can use the `--enable-compatibility-syscall64-size-type` flag for this version.
-The flag will be removed in v1.4.
+* TBD
 
 ### Metrics
 
-* `tetragon_ratelimit_dropped_total` metric is renamed to `tetragon_export_ratelimit_events_dropped_total`
+* TBD

contrib/upgrade-notes/v1.3.0.md

@@ -0,0 +1,47 @@
+## Upgrade notes
+
+Read the upgrade notes carefully before upgrading Tetragon.
+Depending on your setup, changes listed here might require a manual intervention.
+
+* Behavior of `export-file-perm` flag (and corresponding Helm value `tetragon.exportFilePerm`) changed. In case the export file exists, but has different permissions than specified in the option, Tetragon will change the file permissions on the next log rotation. In older versions, log rotation preserved permissions of the existing file. Before upgrading check if permissions of the existing export file match the option (600 by default), and set the agent flag or Helm value to the desired value if needed.
+
+### Agent Options
+
+* TBD
+
+### Helm Values
+
+* TBD
+
+### TracingPolicy (k8s CRD)
+
+* TBD
+
+### Events (protobuf API)
+
+
+#### New events for `syscall64` type
+
+Previous versions of Tetragon did not distinguish between different ABIs when using the syscall64 type
+because the output was just a `size_arg` with the id. When executing the `getcpu` syscall, for example, the JSON
+for 64- and 32-bits would be:
+```
+"args":[{"size_arg":"309"}]
+"args":[{"size_arg":"318"}]
+```
+
+Note that id 318 for `x86_64` is a different syscall: `getrandom` so we cannot distinguish between a `getrandom` syscall on x86_64
+and a `getcpu` call on 32-bit (`i386`). To address this issue, the output of `syscall64` was changed to a `SyscallId` object that
+also includes the ABI. So the JSON for 64- and 32-bits `getcpu` now is:
+
+```
+"args":[{"syscall_id":{"id":309,"abi":"x64"}}]
+"args":[{"syscall_id":{"id":318,"abi":"i386"}}]
+```
+
+Users that want to maintain the old behavior can use the `--enable-compatibility-syscall64-size-type` flag for this version.
+The flag will be removed in v1.4.
+
+### Metrics
+
+* `tetragon_ratelimit_dropped_total` metric is renamed to `tetragon_export_ratelimit_events_dropped_total`

docs/config/_default/hugo.toml

@@ -123,7 +123,7 @@ demo_app_url = "https://raw.githubusercontent.com/cilium/cilium/v1.15.3/examples
 # Used in the "version-banner" partial to display a version number for the
 # current doc set.
 # renovate: datasource=docker depName=quay.io/cilium/tetragon
-version = "v1.2.0"
+version = "v1.3.0"
 
 [params.search.algolia]
 appId = "UI18HE156K"

install/kubernetes/tetragon/Chart.yaml

@@ -2,8 +2,8 @@ apiVersion: v2
 name: tetragon
 description: Helm chart for Tetragon
 type: application
-version: 1.2.0
+version: 1.3.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: 1.2.0
+appVersion: 1.3.0

install/kubernetes/tetragon/values.yaml

@@ -40,7 +40,7 @@ tetragon:
   image:
     override: ~
     repository: quay.io/cilium/tetragon
-    tag: v1.2.1
+    tag: v1.3.0
   resources: {}
   extraArgs: {}
   extraEnv: []
@@ -281,7 +281,7 @@ tetragonOperator:
   image:
     override: ~
     repository: quay.io/cilium/tetragon-operator
-    tag: v1.2.1
+    tag: v1.3.0
     pullPolicy: IfNotPresent
   # -- Extra volumes for the Tetragon Operator Deployment.
   extraVolumes: []