Skip to content

Commit

Permalink
[bitnami/kube-rbac-proxy] Release kube-rbac-proxy-0.18.2-debian-12-r0
Browse files Browse the repository at this point in the history
Signed-off-by: Bitnami Bot <[email protected]>
  • Loading branch information
bitnami-bot committed Nov 29, 2024
1 parent 0900c1f commit ba6fccb
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 9 deletions.
10 changes: 5 additions & 5 deletions bitnami/kube-rbac-proxy/0/debian-12/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"kube-rbac-proxy-0.18.1-4-linux-${OS_ARCH}-debian-12" \
"kube-rbac-proxy-0.18.2-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
Expand All @@ -38,21 +38,21 @@ ENV OS_ARCH="${TARGETARCH:-amd64}"

LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
org.opencontainers.image.base.name="scratch" \
org.opencontainers.image.created="2024-11-07T05:43:17Z" \
org.opencontainers.image.created="2024-11-29T14:52:11Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="0.18.1-debian-12-r4" \
org.opencontainers.image.ref.name="0.18.2-debian-12-r0" \
org.opencontainers.image.title="kube-rbac-proxy" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="0.18.1"
org.opencontainers.image.version="0.18.2"

COPY prebuildfs /
COPY rootfs /
COPY --from=builder /opt/bitnami/kube-rbac-proxy/bin/kube-rbac-proxy /kube-rbac-proxy
COPY --from=builder /opt/bitnami/kube-rbac-proxy/.spdx-kube-rbac-proxy.spdx /opt/bitnami/kube-rbac-proxy/.spdx-kube-rbac-proxy.spdx
COPY --from=builder /opt/bitnami/kube-rbac-proxy/licenses /opt/bitnami/kube-rbac-proxy/licenses

ENV APP_VERSION="0.18.1" \
ENV APP_VERSION="0.18.2" \
BITNAMI_APP_NAME="kube-rbac-proxy"

USER 1001
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,6 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "0.18.1-4"
"version": "0.18.2-0"
}
}
2 changes: 1 addition & 1 deletion bitnami/kube-rbac-proxy/0/debian-12/tags-info.yaml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
rolling-tags:
- "0"
- 0-debian-12
- 0.18.1
- 0.18.2
- latest
4 changes: 2 additions & 2 deletions bitnami/kube-rbac-proxy/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Looking to use Kube RBAC Proxy in production? Try [VMware Tanzu Application Cata

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

Expand Down Expand Up @@ -56,7 +56,7 @@ docker build -t bitnami/APP:latest .

## 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).

## Configuration

Expand Down

0 comments on commit ba6fccb

Please sign in to comment.