From 872c9e39fceb42bf2aa4a55f20fa8d6bdc8c4c04 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Fri, 15 Nov 2024 15:38:26 +0100 Subject: [PATCH] [bitnami/elasticsearch] Release elasticsearch-8.16.0-debian-12-r2 (#74928) Signed-off-by: Bitnami Bot --- bitnami/elasticsearch/8/debian-12/Dockerfile | 4 ++-- bitnami/elasticsearch/README.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/bitnami/elasticsearch/8/debian-12/Dockerfile b/bitnami/elasticsearch/8/debian-12/Dockerfile index 5e2e0e514129..b0138c9068ab 100644 --- a/bitnami/elasticsearch/8/debian-12/Dockerfile +++ b/bitnami/elasticsearch/8/debian-12/Dockerfile @@ -10,11 +10,11 @@ ARG TARGETARCH LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \ org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2024-11-13T09:08:20Z" \ + org.opencontainers.image.created="2024-11-15T14:01:21Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch/README.md" \ org.opencontainers.image.licenses="Apache-2.0" \ - org.opencontainers.image.ref.name="8.16.0-debian-12-r1" \ + org.opencontainers.image.ref.name="8.16.0-debian-12-r2" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch" \ org.opencontainers.image.title="elasticsearch" \ org.opencontainers.image.vendor="Broadcom, Inc." \ diff --git a/bitnami/elasticsearch/README.md b/bitnami/elasticsearch/README.md index c72a333a507e..759747b07f0e 100644 --- a/bitnami/elasticsearch/README.md +++ b/bitnami/elasticsearch/README.md @@ -34,11 +34,11 @@ Bitnami containers can be used with [Kubeapps](https://kubeapps.dev/) for deploy ## Why use a non-root container? -Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-work-with-non-root-containers-index.html). +Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html). ## Supported tags and respective `Dockerfile` links -Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-understand-rolling-tags-containers-index.html). +Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html). You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`.