Deprecate argo-cd 2.13, sonarqube 9, prometheus 2.53 and kubectl 1.31 (#85617)
* Deprecate argo-cd 2.13, sonarqube 9, prometheus 2.53 and kubectl 1.31 Signed-off-by: Carlos Rodríguez Hernández <carlos.rodriguez-hernandez@broadcom.com> * Remove sonarqube branches from goss test Signed-off-by: Carlos Rodríguez Hernández <carlos.rodriguez-hernandez@broadcom.com> --------- Signed-off-by: Carlos Rodríguez Hernández <carlos.rodriguez-hernandez@broadcom.com>
This commit is contained in:
Carlos Rodríguez Hernández
GitHub
parent
83b5a263f0
commit
1cb7e17969
|
|
@ -5,20 +5,6 @@ file:
|
||||||
/opt/bitnami/sonarqube/bin/linux-x86-64/sonar.sh:
|
/opt/bitnami/sonarqube/bin/linux-x86-64/sonar.sh:
|
||||||
exists: true
|
exists: true
|
||||||
filetype: file
|
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:
|
group:
|
||||||
sonarqube:
|
sonarqube:
|
||||||
exists: true
|
exists: true
|
||||||
|
|
|
||||||
|
|
@ -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).
|
|
||||||
|
|
@ -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).
|
|
||||||
|
|
@ -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).
|
|
||||||
|
|
@ -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).
|
|
||||||
Loading…
Reference in New Issue