[bitnami/cert-manager] Release 1.11.2-debian-11-r1 (#33716)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-05-13 08:05:07 +01:00 committed by GitHub
parent 1c70781234
commit ddda0f99a1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 2 deletions

View File

@ -3,10 +3,10 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-05-10T06:35:07Z" \
org.opencontainers.image.created="2023-05-13T06:52:24Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.11.2-debian-11-r0" \
org.opencontainers.image.ref.name="1.11.2-debian-11-r1" \
org.opencontainers.image.title="cert-manager" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="1.11.2"

View File

@ -36,6 +36,8 @@ Kubernetes cluster with `CustomResourceDefinition` or `ThirdPartyResource suppor
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released on a regular basis with the latest distribution packages available.
Looking to use cert-manager in production? Try [VMware Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
## 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.bitnami.com/tutorials/work-with-non-root-containers/).