Merge pull request #325 from anfredette/release-v0.5.4

bpfman-operator release v0.5.4

Author: mergify[bot]

Containerfile.bpfman-agent.openshift

@@ -48,7 +48,7 @@ LABEL name="bpfman/bpfman-agent" \
       description="The bpfman-agent manage bpfman ebpf programs on every node." \
       io.k8s.description="The bpfman-agent manage bpfman programs on every node. ." \
       io.openshift.tags="bpfman-agent" \
-      version="0.5.2" \
+      version="0.5.4" \
       vendor="Red Hat, Inc."
 
 ENTRYPOINT ["/bpfman-agent"]

Containerfile.bpfman-operator.openshift

@@ -42,7 +42,7 @@ LABEL name="bpfman/bpfman-operator" \
       description="The bpfman-operator repository exists to deploy and manage bpfman within a Kubernetes cluster." \
       io.k8s.description="The bpfman-operator repository exists to deploy and manage bpfman within a Kubernetes cluster. ." \
       io.openshift.tags="bpfman-operator" \
-      version="0.5.2" \
+      version="0.5.4" \
       vendor="Red Hat, Inc."
 
 USER 65532:65532

Containerfile.bundle.openshift

@@ -38,8 +38,8 @@ LABEL name="bpfman-operator" \
       distribution-scope=public \
       io.k8s.description="The bpfman-operator manage bpfman programs on every node. ." \
       io.openshift.tags="bpfman-operator" \
-      version="0.5.2" \
-      release="0.5.2" \
+      version="0.5.4" \
+      release="0.5.4" \
       url="https://github.com/bpfman/bpfman-operator" \
       vendor="Red Hat, Inc." \
       summary="Bpfman Operator"

Makefile

@@ -3,7 +3,7 @@
 # To re-generate a bundle for another specific version without changing the standard setup, you can:
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
-VERSION ?= 0.5.2
+VERSION ?= 0.5.4
 
 # CHANNELS define the bundle channels used in the bundle.
 # Add a new line here if you would like to change its default config. (E.g CHANNELS = "candidate,fast,stable")

README.md

@@ -206,7 +206,7 @@ object to find references to the bpfMap pinpoints (`spec.maps`) to configure the
 ## Developer
 
 For more architecture details about `bpfman-operator`, refer to
-[Developing the bpfman-operator](https://bpfman.io/v0.5.2/developer-guide/develop-operator)
+[Developing the bpfman-operator](https://bpfman.io/v0.5.4/developer-guide/develop-operator)
 
 ### Bpfman-agent profiling
 

bundle/manifests/bpfman-operator.clusterserviceversion.yaml

@@ -296,7 +296,7 @@ metadata:
     capabilities: Basic Install
     categories: OpenShift Optional
     containerImage: quay.io/bpfman/bpfman-operator:latest
-    createdAt: "2024-10-15T17:00:13Z"
+    createdAt: "2024-10-17T13:56:37Z"
     features.operators.openshift.io/cnf: "false"
     features.operators.openshift.io/cni: "false"
     features.operators.openshift.io/csi: "true"
@@ -335,7 +335,7 @@ metadata:
     operatorframework.io/arch.arm64: supported
     operatorframework.io/arch.ppc64le: supported
     operatorframework.io/arch.s390x: supported
-  name: bpfman-operator.v0.5.2
+  name: bpfman-operator.v0.5.4
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -1153,4 +1153,4 @@ spec:
   provider:
     name: The bpfman Community
     url: https://bpfman.io/
-  version: 0.5.2
+  version: 0.5.4

changelogs/CHANGELOG-v0.5.1.md

@@ -49,4 +49,10 @@ The v0.5.1 release is a patch release which mainly contains bug fixes and enhanc
 * @frobware made their first contribution in https://github.com/bpfman/bpfman-operator/pull/61
 * @OlivierCazade made their first contribution in https://github.com/bpfman/bpfman-operator/pull/82
 
-**Full Changelog**: https://github.com/bpfman/bpfman-operator/compare/v0.5.0...v0.5.1
+**Full Changelog**: https://github.com/bpfman/bpfman-operator/compare/v0.5.0...v0.5.1
+
+## Known Issues
+* Release v0.5.1 and earlier do not work due to a change in the Cosign API
+  ([Issue 1241](https://github.com/bpfman/bpfman/issues/1241)).  In follow-on
+  releases, whether to use Cosign was made configurable, but for release v0.5.1
+  and earlier, there is no workaround other than to use a later release.

changelogs/CHANGELOG-v0.5.2.md

@@ -17,3 +17,8 @@ ppc64le and s390x, and contains several minor internal updates.
 * @ralphbean made their first contribution in https://github.com/bpfman/bpfman-operator/pull/210
 
 **Full Changelog**: https://github.com/bpfman/bpfman-operator/compare/v0.5.1...v0.5.2
+
+## Known Issues
+* The the OpenShift console should not be used to install the v0.5.2 bpfman
+  community operator because it will use the latest version of the bpfman
+  container image which may or may not work. 

changelogs/CHANGELOG-v0.5.3.md

@@ -0,0 +1,2 @@
+There was no bpfman-operator release v0.5.3 due to an issue with the bpfman
+v0.5.3 release.

changelogs/CHANGELOG-v0.5.4.md

@@ -0,0 +1,8 @@
+The bpfman-operator v0.5.4 release is a patch release that adds support for ppc64le and s390x and also includes some minor internal changes.
+
+## What's Changed
+* Add support for ppc64le and s390x (bpfman change)
+* base clusterserviceversion updates by @anfredette in https://github.com/bpfman/bpfman-operator/pull/323
+* Add separate workflow to run Kubernetes integration tests by @anfredette in https://github.com/bpfman/bpfman-operator/pull/324
+
+**Full Changelog**: https://github.com/bpfman/bpfman-operator/compare/v0.5.2...v0.5.4