From 1cb7e17969306225c62d3c9a8c0547059956de6d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Rodr=C3=ADguez=20Hern=C3=A1ndez?= Date: Thu, 28 Aug 2025 13:27:34 +0200 Subject: [PATCH] Deprecate argo-cd 2.13, sonarqube 9, prometheus 2.53 and kubectl 1.31 (#85617) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Deprecate argo-cd 2.13, sonarqube 9, prometheus 2.53 and kubectl 1.31 Signed-off-by: Carlos Rodríguez Hernández * Remove sonarqube branches from goss test Signed-off-by: Carlos Rodríguez Hernández --------- Signed-off-by: Carlos Rodríguez Hernández --- .vib/sonarqube/goss/sonarqube.yaml | 14 -------------- bitnami/argo-cd/2.13/README.md | 10 ---------- bitnami/kubectl/1.31/README.md | 10 ---------- bitnami/prometheus/2.53/README.md | 10 ---------- bitnami/sonarqube/9/README.md | 10 ---------- 5 files changed, 54 deletions(-) delete mode 100644 bitnami/argo-cd/2.13/README.md delete mode 100644 bitnami/kubectl/1.31/README.md delete mode 100644 bitnami/prometheus/2.53/README.md delete mode 100644 bitnami/sonarqube/9/README.md diff --git a/.vib/sonarqube/goss/sonarqube.yaml b/.vib/sonarqube/goss/sonarqube.yaml index c240240c1aae..01f3e99c72c9 100644 --- a/.vib/sonarqube/goss/sonarqube.yaml +++ b/.vib/sonarqube/goss/sonarqube.yaml @@ -5,20 +5,6 @@ file: /opt/bitnami/sonarqube/bin/linux-x86-64/sonar.sh: exists: true filetype: file - contents: - {{ if regexMatch "^8.+" .Env.APP_VERSION }} - - "PIDDIR=\"../../pids\"" - {{ else if regexMatch "^9.+" .Env.APP_VERSION }} - - "PIDFILE=\"/opt/bitnami/sonarqube/pids/$APP_NAME.pid\"" - {{ end }} - # Test specific for branch@8 - {{ if regexMatch "^8.+" .Env.APP_VERSION }} - /opt/bitnami/sonarqube/conf/wrapper.conf: - exists: true - filetype: file - contents: - - "wrapper.logfile.rollmode=NONE" - {{ end }} group: sonarqube: exists: true diff --git a/bitnami/argo-cd/2.13/README.md b/bitnami/argo-cd/2.13/README.md deleted file mode 100644 index 04c96f8c1d98..000000000000 --- a/bitnami/argo-cd/2.13/README.md +++ /dev/null @@ -1,10 +0,0 @@ -# ⚠️ Important Notice: Upcoming changes to the Bitnami Catalog - -Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new [Bitnami Secure Images initiative](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications). As part of this transition: - -- Granting community users access for the first time to security-optimized versions of popular container images. -- Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes -- Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates. -- For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support. - -These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the [Bitnami Secure Images announcement](https://github.com/bitnami/containers/issues/83267). diff --git a/bitnami/kubectl/1.31/README.md b/bitnami/kubectl/1.31/README.md deleted file mode 100644 index 04c96f8c1d98..000000000000 --- a/bitnami/kubectl/1.31/README.md +++ /dev/null @@ -1,10 +0,0 @@ -# ⚠️ Important Notice: Upcoming changes to the Bitnami Catalog - -Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new [Bitnami Secure Images initiative](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications). As part of this transition: - -- Granting community users access for the first time to security-optimized versions of popular container images. -- Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes -- Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates. -- For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support. - -These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the [Bitnami Secure Images announcement](https://github.com/bitnami/containers/issues/83267). diff --git a/bitnami/prometheus/2.53/README.md b/bitnami/prometheus/2.53/README.md deleted file mode 100644 index 04c96f8c1d98..000000000000 --- a/bitnami/prometheus/2.53/README.md +++ /dev/null @@ -1,10 +0,0 @@ -# ⚠️ Important Notice: Upcoming changes to the Bitnami Catalog - -Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new [Bitnami Secure Images initiative](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications). As part of this transition: - -- Granting community users access for the first time to security-optimized versions of popular container images. -- Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes -- Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates. -- For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support. - -These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the [Bitnami Secure Images announcement](https://github.com/bitnami/containers/issues/83267). diff --git a/bitnami/sonarqube/9/README.md b/bitnami/sonarqube/9/README.md deleted file mode 100644 index 04c96f8c1d98..000000000000 --- a/bitnami/sonarqube/9/README.md +++ /dev/null @@ -1,10 +0,0 @@ -# ⚠️ Important Notice: Upcoming changes to the Bitnami Catalog - -Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new [Bitnami Secure Images initiative](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications). As part of this transition: - -- Granting community users access for the first time to security-optimized versions of popular container images. -- Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes -- Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates. -- For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support. - -These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the [Bitnami Secure Images announcement](https://github.com/bitnami/containers/issues/83267).