HUB
Sign inSign up
Kubeflow Pipelines - Inverse Proxy Agent

dhi.io/kubeflow-pipelines-inverse-proxy-agent

Kubeflow Pipelines - Inverse Proxy Agent

CIS
FIPS
STIG
linux/amd64
linux/arm64

The Kubeflow Pipelines inverse proxy agent connects the Pipelines UI in a Kubernetes cluster to a Google Cloud inverting proxy, so the UI can be reached without exposing a public endpoint.

Image

pushed 1 hour ago

View image detail
Platforms

linux/amd64, linux/arm64

Size

108.37 MB

for linux/amd64

Packages

346

for linux/amd64

Support

Active support

Tools included

proxy-forwarding-agent, gcloud, kubectl

What's includedWhy it matters
SLSA Provenance

Build Level 3

Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.

SBOM

CycloneDX SBOM + SPDX SBOM

A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.

VEX

A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.

DHI Image Sources

Available

A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.

CVEs
0
2
8
8
1

Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.

Changelog

-

Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.

Secrets scan

Verifies no keys, tokens, or credentials were accidentally baked into the image.

Virus scan

The image layers were scanned for known malware signatures before publishing.


About Kubeflow Pipelines - Inverse Proxy Agent

The Kubeflow Pipelines inverse proxy agent makes the Kubeflow Pipelines UI in a Google Kubernetes Engine (GKE) cluster reachable through Google's inverting proxy, without exposing a public endpoint or load balancer. It runs as a single pod next to the Pipelines UI Service and keeps an outbound connection to the proxy, which relays browser requests back to the UI.

On startup, the launcher reuses the proxy registration stored in the inverse-proxy-config ConfigMap, or registers a new backend using the node's Google Cloud identity and records the result there. See the Kubeflow Pipelines documentation⁠ for details.

About Docker Hardened Images

Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.

Why use Docker Hardened Images?

These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.

Trademarks

Kubeflow® is a trademark of the Linux Foundation. Google Cloud™ is a trademark of Google LLC. All rights in the marks are reserved to their respective owners. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.