[bitnami/hubble-relay] Release 1.15.5-debian-12-r0 (#67394)
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
GitHub
parent
263ed3152c
commit
9b034d3ee8
|
|
@ -7,7 +7,7 @@ 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-05-27T13:35:28Z" \
|
||||
org.opencontainers.image.created="2024-06-03T12:10:49Z" \
|
||||
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" \
|
||||
|
|
@ -30,7 +30,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
|
|||
COMPONENTS=( \
|
||||
"grpc-health-probe-0.4.26-0-linux-${OS_ARCH}-debian-12" \
|
||||
"gops-0.3.28-1-linux-${OS_ARCH}-debian-12" \
|
||||
"hubble-relay-1.15.5-0-linux-${OS_ARCH}-debian-12" \
|
||||
"hubble-1.15.5-0-linux-${OS_ARCH}-debian-12" \
|
||||
) ; \
|
||||
for COMPONENT in "${COMPONENTS[@]}"; do \
|
||||
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
|
||||
|
|
@ -47,13 +47,14 @@ RUN apt-get autoremove --purge -y curl && \
|
|||
RUN chmod g+rwX /opt/bitnami
|
||||
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
|
||||
|
||||
RUN ln -sf /opt/bitnami/hubble /opt/bitnami/hubble-relay
|
||||
ENV APP_VERSION="1.15.5" \
|
||||
BITNAMI_APP_NAME="hubble-relay" \
|
||||
PATH="/opt/bitnami/common/bin:/opt/bitnami/hubble-relay/bin:$PATH"
|
||||
PATH="/opt/bitnami/common/bin:/opt/bitnami/hubble/bin:$PATH"
|
||||
|
||||
EXPOSE 6062 9893 9966
|
||||
EXPOSE 4245 6062 9893 9966
|
||||
|
||||
WORKDIR /opt/bitnami/hubble-relay
|
||||
WORKDIR /opt/bitnami/hubble
|
||||
USER 1001
|
||||
ENTRYPOINT [ "/opt/bitnami/hubble-relay/bin/hubble-relay" ]
|
||||
ENTRYPOINT [ "/opt/bitnami/hubble/bin/hubble-relay" ]
|
||||
CMD [ "help" ]
|
||||
|
|
|
|||
|
|
@ -4,5 +4,6 @@
|
|||
version: "2"
|
||||
|
||||
services:
|
||||
hubble-relay:
|
||||
hubble:
|
||||
image: docker.io/bitnami/hubble-relay:1
|
||||
container_name: hubble-relay
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
"type": "NAMI",
|
||||
"version": "0.4.26-0"
|
||||
},
|
||||
"hubble-relay": {
|
||||
"hubble": {
|
||||
"arch": "amd64",
|
||||
"distro": "debian-12",
|
||||
"type": "NAMI",
|
||||
|
|
|
|||
|
|
@ -1,14 +1,16 @@
|
|||
# Bitnami package for Hubble Relay
|
||||
# Bitnami package for Hubble
|
||||
|
||||
## What is Hubble Relay?
|
||||
|
||||
> Hubble Relay collects eBPF-based visibility data from every running Hubble server in a cluster by connecting to their respective gRPC APIs and providing an unique API that represents all of them.
|
||||
|
||||
[Overview of Hubble Relay](https://cilium.io/)
|
||||
[Overview of Hubble](https://cilium.io/)
|
||||
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
|
||||
|
||||
## TL;DR
|
||||
|
||||
This container is part of the [Hubble chart](https://github.com/bitnami/charts/tree/main/bitnami/hubble) that is primarily intended to be deployed in Kubernetes.
|
||||
|
||||
```console
|
||||
docker run --name hubble-relay bitnami/hubble-relay:latest
|
||||
```
|
||||
|
|
@ -24,6 +26,12 @@ docker run --name hubble-relay bitnami/hubble-relay:latest
|
|||
|
||||
Looking to use Hubble Relay in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
|
||||
|
||||
## How to deploy Hubble in Kubernetes?
|
||||
|
||||
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Hubble Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/harbor).
|
||||
|
||||
Bitnami containers can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
|
||||
|
||||
## 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).
|
||||
|
|
@ -62,13 +70,13 @@ docker build -t bitnami/APP:latest .
|
|||
|
||||
### Running commands
|
||||
|
||||
To run commands inside this container you can use `docker run`, for example to execute `hubble-relay-generic help` you can follow the example below:
|
||||
To run commands inside this container you can use `docker run`, for example to execute `hubble-relay help` you can follow the example below:
|
||||
|
||||
```console
|
||||
docker run --rm --name hubble-relay bitnami/hubble-relay:latest help
|
||||
```
|
||||
|
||||
Check the [official Hubble Relay documentation](https://docs.cilium.io/en/stable/internals/hubble/) for more information about configuration options.
|
||||
Check the [official Hubble documentation](https://docs.cilium.io/en/stable/internals/hubble/) for more information about configuration options.
|
||||
|
||||
## Contributing
|
||||
|
||||
|
|
|
|||
|
|
@ -4,5 +4,6 @@
|
|||
version: "2"
|
||||
|
||||
services:
|
||||
hubble-relay:
|
||||
hubble:
|
||||
image: docker.io/bitnami/hubble-relay:1
|
||||
container_name: hubble-relay
|
||||
|
|
|
|||
Loading…
Reference in New Issue