Prepare release v1.0.3

Makefile

@@ -24,13 +24,13 @@ REPO ?= quay.io/$(IMAGE_ORG)
 
 # Component versions to use in bundle / release (do not use $VERSION for that)
 PREVIOUS_VERSION ?= v1.0.2
-BUNDLE_VERSION ?= 1.0.3-rc0
+BUNDLE_VERSION ?= 1.0.3
 # console plugin
-export PLG_VERSION ?= v0.1.10-rc0
+export PLG_VERSION ?= v0.1.10
 # flowlogs-pipeline
-export FLP_VERSION ?= v0.1.9-rc2
+export FLP_VERSION ?= v0.1.9
 # eBPF agent
-export BPF_VERSION ?= v0.3.1-rc0
+export BPF_VERSION ?= v0.3.1
 
 # Allows building bundles in Mac replacing BSD 'sed' command by GNU-compatible 'gsed'
 ifeq (,$(shell which gsed 2>/dev/null))

RELEASE.md

@@ -36,7 +36,7 @@ Edit the [Makefile](./Makefile) to update `PREVIOUS_VERSION`, `BUNDLE_VERSION`,
 make update-bundle
 
 # Set desired operator version - CAREFUL, no leading "v" here
-version="1.0.3-rc0"
+version="1.0.3"
 vv=v$version
 test_branch=test-$vv
 
@@ -52,7 +52,7 @@ The release script should be triggered ([check github actions](https://github.co
 At this point, you can test the bundle / catalog on your cluster:
 
 ```bash
-BUNDLE_VERSION="$version" make catalog-deploy
+BUNDLE_VERSION="$version" USER=netobserv make catalog-deploy
 ```
 
 When everything is ok, push to main and delete the test branch

bundle/manifests/netobserv-operator.clusterserviceversion.yaml

@@ -347,7 +347,7 @@ metadata:
     capabilities: Seamless Upgrades
     categories: Monitoring
     console.openshift.io/plugins: '["netobserv-plugin"]'
-    containerImage: quay.io/netobserv/network-observability-operator:1.0.3-rc0
+    containerImage: quay.io/netobserv/network-observability-operator:1.0.3
     createdAt: ':created-at:'
     description: Network flows collector and monitoring solution
     operatorframework.io/suggested-namespace: openshift-netobserv-operator
@@ -359,7 +359,7 @@ metadata:
     operatorframework.io/arch.arm64: supported
     operatorframework.io/arch.ppc64le: supported
     operatorframework.io/os.linux: supported
-  name: netobserv-operator.v1.0.3-rc0
+  name: netobserv-operator.v1.0.3
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -412,7 +412,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.0.3-rc0/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.0.3-rc0/config/samples/flows_v1beta1_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.0.3/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.0.3/config/samples/flows_v1beta1_flowcollector.yaml).
 
     To edit configuration in cluster, run:
 
@@ -430,7 +430,7 @@ spec:
 
     - Loki (`spec.loki`): configure here how to reach Loki. The default values match the Loki quick install paths mentioned above, but you may have to configure differently if you used another installation method.
 
-    - 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.0.3-rc0/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.0.3/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.
 
@@ -683,14 +683,14 @@ spec:
                 - /manager
                 env:
                 - name: RELATED_IMAGE_EBPF_AGENT
-                  value: quay.io/netobserv/netobserv-ebpf-agent:v0.3.1-rc0
+                  value: quay.io/netobserv/netobserv-ebpf-agent:v0.3.1
                 - name: RELATED_IMAGE_FLOWLOGS_PIPELINE
-                  value: quay.io/netobserv/flowlogs-pipeline:v0.1.9-rc2
+                  value: quay.io/netobserv/flowlogs-pipeline:v0.1.9
                 - name: RELATED_IMAGE_CONSOLE_PLUGIN
-                  value: quay.io/netobserv/network-observability-console-plugin:v0.1.10-rc0
+                  value: quay.io/netobserv/network-observability-console-plugin:v0.1.10
                 - name: DOWNSTREAM_DEPLOYMENT
                   value: "false"
-                image: quay.io/netobserv/network-observability-operator:1.0.3-rc0
+                image: quay.io/netobserv/network-observability-operator:1.0.3
                 imagePullPolicy: Always
                 livenessProbe:
                   httpGet:
@@ -839,14 +839,14 @@ spec:
     name: Red Hat
     url: https://www.redhat.com
   relatedImages:
-  - image: quay.io/netobserv/netobserv-ebpf-agent:v0.3.1-rc0
+  - image: quay.io/netobserv/netobserv-ebpf-agent:v0.3.1
     name: ebpf-agent
-  - image: quay.io/netobserv/flowlogs-pipeline:v0.1.9-rc2
+  - image: quay.io/netobserv/flowlogs-pipeline:v0.1.9
     name: flowlogs-pipeline
-  - image: quay.io/netobserv/network-observability-console-plugin:v0.1.10-rc0
+  - image: quay.io/netobserv/network-observability-console-plugin:v0.1.10
     name: console-plugin
   replaces: netobserv-operator.v1.0.2
-  version: 1.0.3-rc0
+  version: 1.0.3
   webhookdefinitions:
   - admissionReviewVersions:
     - v1alpha1

config/manager/kustomization.yaml

@@ -15,6 +15,6 @@ kind: Kustomization
 images:
 - name: controller
   newName: quay.io/netobserv/network-observability-operator
-  newTag: 1.0.3-rc0
+  newTag: 1.0.3
 commonLabels:
   app: netobserv-operator

config/manager/manager.yaml

@@ -30,11 +30,11 @@ spec:
         - --downstream-deployment=$(DOWNSTREAM_DEPLOYMENT)
         env:
           - name: RELATED_IMAGE_EBPF_AGENT
-            value: quay.io/netobserv/netobserv-ebpf-agent:v0.3.1-rc0
+            value: quay.io/netobserv/netobserv-ebpf-agent:v0.3.1
           - name: RELATED_IMAGE_FLOWLOGS_PIPELINE
-            value: quay.io/netobserv/flowlogs-pipeline:v0.1.9-rc2
+            value: quay.io/netobserv/flowlogs-pipeline:v0.1.9
           - name: RELATED_IMAGE_CONSOLE_PLUGIN
-            value: quay.io/netobserv/network-observability-console-plugin:v0.1.10-rc0
+            value: quay.io/netobserv/network-observability-console-plugin:v0.1.10
           - name: DOWNSTREAM_DEPLOYMENT
             value: "false"
         image: controller:latest

config/manifests/bases/description-ocp.md

@@ -32,7 +32,7 @@ oc apply -f <(curl -L https://raw.githubusercontent.com/netobserv/documents/252b
 
 ## 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.0.3-rc0/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.0.3-rc0/config/samples/flows_v1beta1_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.0.3/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.0.3/config/samples/flows_v1beta1_flowcollector.yaml).
 
 To edit configuration in cluster, run:
 
@@ -48,7 +48,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 may have to configure differently if you used another installation method.
 
-- 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.0.3-rc0/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.0.3/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.
 

config/manifests/bases/description-upstream.md

@@ -32,7 +32,7 @@ kubectl apply -f <(curl -L https://raw.githubusercontent.com/netobserv/documents
 
 ## 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.0.3-rc0/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.0.3-rc0/config/samples/flows_v1beta1_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.0.3/docs/FlowCollector.md), and a full sample file [there](https://github.com/netobserv/network-observability-operator/blob/1.0.3/config/samples/flows_v1beta1_flowcollector.yaml).
 
 To edit configuration in cluster, run:
 
@@ -50,7 +50,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 may have to configure differently if you used another installation method.
 
-- 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.0.3-rc0/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.0.3/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.