Prepare release v1.9.2-community

Author: jotak

Makefile

@@ -15,15 +15,13 @@ IMAGE_REGISTRY ?= quay.io
 REPO ?= $(IMAGE_REGISTRY)/$(IMAGE_ORG)
 
 # Component versions to use in bundle / release (do not use $VERSION for that)
-BUNDLE_VERSION ?= 1.9.1-community
-#File based catalog
-FBC_VERSION ?= 1.9.1-community
+BUNDLE_VERSION ?= 1.9.2-community
 # console plugin
-export PLG_VERSION ?= v1.9.1-community
+export PLG_VERSION ?= v${BUNDLE_VERSION}
 # flowlogs-pipeline
-export FLP_VERSION ?= v1.9.1-community
+export FLP_VERSION ?= v${BUNDLE_VERSION}
 # eBPF agent
-export BPF_VERSION ?= v1.9.1-community
+export BPF_VERSION ?= v${BUNDLE_VERSION}
 
 # Allows building bundles in Mac replacing BSD 'sed' command by GNU-compatible 'gsed'
 ifeq (,$(shell which gsed 2>/dev/null))

RELEASE.md

@@ -1,23 +1,59 @@
 ## Releasing process
 
-### Sub-components
+### Related components - draft release
 
 All components deployed by this operator can be released separatly, at their own pace.
 
-Before releasing, it's a good opportunity to check for image upgrades: Go, [node.js](https://catalog.redhat.com/software/containers/ubi9/nodejs-18/62e8e7ed22d1d3c2dfe2ca01) and [ubi9-minimal](https://catalog.redhat.com/software/containers/ubi9-minimal/61832888c0d15aff4912fe0d).
-
 To release them, a tag in the format "v1.6.0-community" or "v1.6.0-crc0" must be set on the desired clean HEAD state (generally, up-to-date `main` branch; "crc" stands for "community release candidate"), then pushed. It applies to [the console plugin](https://github.com/netobserv/network-observability-console-plugin/), [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline) and [netobserv-ebpf-agent](https://github.com/netobserv/netobserv-ebpf-agent).
 
 E.g:
 
 ```bash
-version="v1.9.1-community"
+version="v1.9.2-community"
 git tag -a "$version" -m "$version"
 git push upstream --tags
 ```
 
 The release script should be triggered (check github actions). It will automatically draft a new release, with artifacts attached.
 
+### Operator - draft release
+
+When all those components are pre-released, we can proceed with the operator.
+
+Edit the [Makefile](./Makefile) to update `BUNDLE_VERSION`.
+
+```bash
+make update-bundle
+
+# Set desired operator version - CAREFUL, no leading "v" here
+version="1.9.2-community"
+vv=v$version
+test_branch=test-$vv
+
+git commit -a -m "Prepare release $vv"
+# Push to a test branch, and tag for release
+git push upstream HEAD:$test_branch
+git tag -a "$version" -m "$version"
+git push upstream --tags
+```
+
+The release script should be triggered ([check github actions](https://github.com/netobserv/network-observability-operator/actions)).
+
+At this point, you can test the bundle / catalog on your cluster:
+
+```bash
+BUNDLE_VERSION="$version" USER=netobserv make catalog-deploy
+```
+
+When everything is ok, push to main and delete the test branch
+
+```bash
+git push upstream HEAD:main
+git push upstream :$test_branch
+```
+
+
+
 If the release looks good, you can publish it via the github interface:
 - [console plugin](https://github.com/netobserv/network-observability-console-plugin/releases)
 - [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline/releases)

bundle/manifests/netobserv-operator.clusterserviceversion.yaml

@@ -252,8 +252,8 @@ metadata:
     capabilities: Seamless Upgrades
     categories: Monitoring, Networking, Observability
     console.openshift.io/plugins: '["netobserv-plugin"]'
-    containerImage: quay.io/netobserv/network-observability-operator:1.9.1-community
-    createdAt: "2025-09-05T12:42:59Z"
+    containerImage: quay.io/netobserv/network-observability-operator:1.9.2-community
+    createdAt: "2025-09-08T08:23:26Z"
     description: Network flows collector and monitoring solution
     operatorframework.io/initialization-resource: '{"apiVersion":"flows.netobserv.io/v1beta2",
       "kind":"FlowCollector","metadata":{"name":"cluster"},"spec": {}}'
@@ -268,7 +268,7 @@ metadata:
     operatorframework.io/arch.ppc64le: supported
     operatorframework.io/arch.s390x: supported
     operatorframework.io/os.linux: supported
-  name: netobserv-operator.v1.9.1-community
+  name: netobserv-operator.v1.9.2-community
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -706,7 +706,7 @@ spec:
 
     ## Configuration
 
-    The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/config/samples/flows_v1beta2_flowcollector.yaml).
+    The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/config/samples/flows_v1beta2_flowcollector.yaml).
 
     To edit configuration in cluster, run:
 
@@ -722,7 +722,7 @@ spec:
 
     - Loki (`spec.loki`): configure here how to reach Loki. The default values match the Loki quick install paths mentioned above, but you might have to configure differently if you used another installation method. Make sure to disable it (`spec.loki.enable`) if you don't want to use Loki.
 
-    - Quick filters (`spec.consolePlugin.quickFilters`): configure preset filters to be displayed in the Console plugin. They offer a way to quickly switch from filters to others, such as showing / hiding pods network, or infrastructure network, or application network, etc. They can be tuned to reflect the different workloads running on your cluster. For a list of available filters, [check this page](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/QuickFilters.md).
+    - Quick filters (`spec.consolePlugin.quickFilters`): configure preset filters to be displayed in the Console plugin. They offer a way to quickly switch from filters to others, such as showing / hiding pods network, or infrastructure network, or application network, etc. They can be tuned to reflect the different workloads running on your cluster. For a list of available filters, [check this page](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/QuickFilters.md).
 
     - Kafka (`spec.deploymentModel: KAFKA` and `spec.kafka`): when enabled, integrates the flow collection pipeline with Kafka, by splitting ingestion from transformation (kube enrichment, derived metrics, ...). Kafka can provide better scalability, resiliency and high availability ([view more details](https://www.redhat.com/en/topics/integration/what-is-apache-kafka)). Assumes Kafka is already deployed and a topic is created.
 
@@ -758,7 +758,7 @@ spec:
     This documentation includes:
 
     - An [overview](https://github.com/netobserv/network-observability-operator#openshift-console) of the features, with screenshots
-    - More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/Metrics.md).
+    - More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/Metrics.md).
     - A [performance](https://github.com/netobserv/network-observability-operator#performance-fine-tuning) section, for fine-tuning
     - A [security](https://github.com/netobserv/network-observability-operator#securing-data-and-communications) section
     - An [F.A.Q.](https://github.com/netobserv/network-observability-operator#faq--troubleshooting) section
@@ -1064,11 +1064,11 @@ spec:
                 - /manager
                 env:
                 - name: RELATED_IMAGE_EBPF_AGENT
-                  value: quay.io/netobserv/netobserv-ebpf-agent:v1.9.1-community
+                  value: quay.io/netobserv/netobserv-ebpf-agent:v1.9.2-community
                 - name: RELATED_IMAGE_FLOWLOGS_PIPELINE
-                  value: quay.io/netobserv/flowlogs-pipeline:v1.9.1-community
+                  value: quay.io/netobserv/flowlogs-pipeline:v1.9.2-community
                 - name: RELATED_IMAGE_CONSOLE_PLUGIN
-                  value: quay.io/netobserv/network-observability-console-plugin:v1.9.1-community
+                  value: quay.io/netobserv/network-observability-console-plugin:v1.9.2-community
                 - name: RELATED_IMAGE_CONSOLE_PLUGIN_COMPAT
                   value: quay.io/netobserv/network-observability-console-plugin-pf4:v1.8.2-community
                 - name: DOWNSTREAM_DEPLOYMENT
@@ -1078,7 +1078,7 @@ spec:
                   valueFrom:
                     fieldRef:
                       fieldPath: metadata.namespace
-                image: quay.io/netobserv/network-observability-operator:1.9.1-community
+                image: quay.io/netobserv/network-observability-operator:1.9.2-community
                 imagePullPolicy: Always
                 livenessProbe:
                   httpGet:
@@ -1210,15 +1210,15 @@ spec:
     name: Red Hat
     url: https://www.redhat.com
   relatedImages:
-  - image: quay.io/netobserv/netobserv-ebpf-agent:v1.9.1-community
+  - image: quay.io/netobserv/netobserv-ebpf-agent:v1.9.2-community
     name: ebpf-agent
-  - image: quay.io/netobserv/flowlogs-pipeline:v1.9.1-community
+  - image: quay.io/netobserv/flowlogs-pipeline:v1.9.2-community
     name: flowlogs-pipeline
-  - image: quay.io/netobserv/network-observability-console-plugin:v1.9.1-community
+  - image: quay.io/netobserv/network-observability-console-plugin:v1.9.2-community
     name: console-plugin
   - image: quay.io/netobserv/network-observability-console-plugin-pf4:v1.8.2-community
     name: console-plugin-compat
-  version: 1.9.1-community
+  version: 1.9.2-community
   webhookdefinitions:
   - admissionReviewVersions:
     - v1

config/descriptions/ocp.md

@@ -38,7 +38,7 @@ In that case, you can still get the Prometheus metrics or export raw flows to a
 
 ## Configuration
 
-The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/config/samples/flows_v1beta2_flowcollector.yaml).
+The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/config/samples/flows_v1beta2_flowcollector.yaml).
 
 To edit configuration in cluster, run:
 
@@ -54,7 +54,7 @@ A couple of settings deserve special attention:
 
 - Loki (`spec.loki`): configure here how to reach Loki. The default values match the Loki quick install paths mentioned above, but you might have to configure differently if you used another installation method. Make sure to disable it (`spec.loki.enable`) if you don't want to use Loki.
 
-- Quick filters (`spec.consolePlugin.quickFilters`): configure preset filters to be displayed in the Console plugin. They offer a way to quickly switch from filters to others, such as showing / hiding pods network, or infrastructure network, or application network, etc. They can be tuned to reflect the different workloads running on your cluster. For a list of available filters, [check this page](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/QuickFilters.md).
+- Quick filters (`spec.consolePlugin.quickFilters`): configure preset filters to be displayed in the Console plugin. They offer a way to quickly switch from filters to others, such as showing / hiding pods network, or infrastructure network, or application network, etc. They can be tuned to reflect the different workloads running on your cluster. For a list of available filters, [check this page](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/QuickFilters.md).
 
 - Kafka (`spec.deploymentModel: KAFKA` and `spec.kafka`): when enabled, integrates the flow collection pipeline with Kafka, by splitting ingestion from transformation (kube enrichment, derived metrics, ...). Kafka can provide better scalability, resiliency and high availability ([view more details](https://www.redhat.com/en/topics/integration/what-is-apache-kafka)). Assumes Kafka is already deployed and a topic is created.
 
@@ -90,7 +90,7 @@ Please refer to the documentation on GitHub for more information.
 This documentation includes:
 
 - An [overview](https://github.com/netobserv/network-observability-operator#openshift-console) of the features, with screenshots
-- More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/Metrics.md).
+- More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/Metrics.md).
 - A [performance](https://github.com/netobserv/network-observability-operator#performance-fine-tuning) section, for fine-tuning
 - A [security](https://github.com/netobserv/network-observability-operator#securing-data-and-communications) section
 - An [F.A.Q.](https://github.com/netobserv/network-observability-operator#faq--troubleshooting) section

config/descriptions/upstream.md

@@ -42,7 +42,7 @@ In that case, you can still get the Prometheus metrics or export raw flows to a
 
 ## Configuration
 
-The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/config/samples/flows_v1beta2_flowcollector.yaml).
+The `FlowCollector` resource is used to configure the operator and its managed components. A comprehensive documentation is [available here](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/config/samples/flows_v1beta2_flowcollector.yaml).
 
 To edit configuration in cluster, run:
 
@@ -58,7 +58,7 @@ A couple of settings deserve special attention:
 
 - Loki (`spec.loki`): configure here how to reach Loki. The default values match the Loki quick install paths mentioned above, but you might have to configure differently if you used another installation method. Make sure to disable it (`spec.loki.enable`) if you don't want to use Loki.
 
-- Quick filters (`spec.consolePlugin.quickFilters`): configure preset filters to be displayed in the Console plugin. They offer a way to quickly switch from filters to others, such as showing / hiding pods network, or infrastructure network, or application network, etc. They can be tuned to reflect the different workloads running on your cluster. For a list of available filters, [check this page](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/QuickFilters.md).
+- Quick filters (`spec.consolePlugin.quickFilters`): configure preset filters to be displayed in the Console plugin. They offer a way to quickly switch from filters to others, such as showing / hiding pods network, or infrastructure network, or application network, etc. They can be tuned to reflect the different workloads running on your cluster. For a list of available filters, [check this page](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/QuickFilters.md).
 
 - Kafka (`spec.deploymentModel: KAFKA` and `spec.kafka`): when enabled, integrates the flow collection pipeline with Kafka, by splitting ingestion from transformation (kube enrichment, derived metrics, ...). Kafka can provide better scalability, resiliency and high availability ([view more details](https://www.redhat.com/en/topics/integration/what-is-apache-kafka)). Assumes Kafka is already deployed and a topic is created.
 
@@ -94,7 +94,7 @@ Please refer to the documentation on GitHub for more information.
 This documentation includes:
 
 - An [overview](https://github.com/netobserv/network-observability-operator#openshift-console) of the features, with screenshots
-- More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.9.1-community/docs/Metrics.md).
+- More information on [configuring metrics](https://github.com/netobserv/network-observability-operator/blob/1.9.2-community/docs/Metrics.md).
 - A [performance](https://github.com/netobserv/network-observability-operator#performance-fine-tuning) section, for fine-tuning
 - A [security](https://github.com/netobserv/network-observability-operator#securing-data-and-communications) section
 - An [F.A.Q.](https://github.com/netobserv/network-observability-operator#faq--troubleshooting) section

config/manager/kustomization.yaml

@@ -14,7 +14,7 @@ patches:
 images:
 - name: controller
   newName: quay.io/netobserv/network-observability-operator
-  newTag: 1.9.1-community
+  newTag: 1.9.2-community
 labels:
 - includeSelectors: true
   pairs:

config/manager/manager.yaml

@@ -33,11 +33,11 @@ spec:
         - --profiling-bind-address=$(PROFILING_BIND_ADDRESS)
         env:
           - name: RELATED_IMAGE_EBPF_AGENT
-            value: quay.io/netobserv/netobserv-ebpf-agent:v1.9.1-community
+            value: quay.io/netobserv/netobserv-ebpf-agent:v1.9.2-community
           - name: RELATED_IMAGE_FLOWLOGS_PIPELINE
-            value: quay.io/netobserv/flowlogs-pipeline:v1.9.1-community
+            value: quay.io/netobserv/flowlogs-pipeline:v1.9.2-community
           - name: RELATED_IMAGE_CONSOLE_PLUGIN
-            value: quay.io/netobserv/network-observability-console-plugin:v1.9.1-community
+            value: quay.io/netobserv/network-observability-console-plugin:v1.9.2-community
           - name: RELATED_IMAGE_CONSOLE_PLUGIN_COMPAT
             value: quay.io/netobserv/network-observability-console-plugin-pf4:v1.8.2-community
           - name: DOWNSTREAM_DEPLOYMENT

helm/Chart.yaml

@@ -15,13 +15,13 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.9.1
+version: 1.9.2
 
 # 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.
 # It is recommended to use it with quotes.
-appVersion: 1.9.1-community
+appVersion: 1.9.2-community
 
 keywords:
 - network observability

helm/values.yaml

@@ -8,20 +8,20 @@ certManager:
 # Deployment manifest values
 ebpfAgent:
   image: quay.io/netobserv/netobserv-ebpf-agent
-  version: v1.9.1-community
+  version: v1.9.2-community
 flowlogsPipeline:
   image: quay.io/netobserv/flowlogs-pipeline
-  version: v1.9.1-community
+  version: v1.9.2-community
 consolePlugin:
   image: quay.io/netobserv/network-observability-console-plugin
-  version: v1.9.1-community
+  version: v1.9.2-community
 standaloneConsole:
   enable: false
   image: quay.io/netobserv/network-observability-standalone-frontend
-  version: v1.9.1-community
+  version: v1.9.2-community
 operator:
   image: quay.io/netobserv/network-observability-operator
-  version: 1.9.1-community
+  version: 1.9.2-community
   # Node affinity configuration for the operator deployment
   nodeAffinity: {}
   # Example: