[bitnami/hubble-relay] Release hubble-relay-1.16.4-debian-12-r0 (#75009)

Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-11-19 17:24:42 +01:00
committed by GitHub
parent 706851782b
commit e924635c3a
4 changed files with 9 additions and 9 deletions

View File

@@ -8,15 +8,15 @@ 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-09T21:03:57Z" \
org.opencontainers.image.created="2024-11-19T16:04:21Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/hubble-relay/README.md" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.16.3-debian-12-r3" \
org.opencontainers.image.ref.name="1.16.4-debian-12-r0" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/hubble-relay" \
org.opencontainers.image.title="hubble-relay" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="1.16.3"
org.opencontainers.image.version="1.16.4"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -31,7 +31,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"grpc-health-probe-0.4.35-1-linux-${OS_ARCH}-debian-12" \
"gops-0.3.28-10-linux-${OS_ARCH}-debian-12" \
"hubble-relay-1.16.3-2-linux-${OS_ARCH}-debian-12" \
"hubble-relay-1.16.4-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -48,7 +48,7 @@ RUN apt-get autoremove --purge -y curl && \
RUN chmod g+rwX /opt/bitnami
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
ENV APP_VERSION="1.16.3" \
ENV APP_VERSION="1.16.4" \
BITNAMI_APP_NAME="hubble-relay" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/hubble-relay/bin:$PATH"

View File

@@ -15,6 +15,6 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "1.16.3-2"
"version": "1.16.4-0"
}
}

View File

@@ -1,5 +1,5 @@
rolling-tags:
- "1"
- 1-debian-12
- 1.16.3
- 1.16.4
- latest

View File

@@ -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`.