Skip to main content

πŸ’Ύ Shared Disk Among Namespaces

πŸ€” Why Do I Need This?​

Have you ever needed to crunch data against the massive, shared ingestion dataset, but your pod is stuck in a different development or staging namespace?

We maintain a central disk holding all this vital data, but a strict Kubernetes limitation prevents a single Persistent Volume Claim (PVC) from being shared across multiple namespaces! πŸ›‘

The Solution: This handy Jenkins pipeline! πŸ› οΈ

It automatically creates a special "shortcut"β€”a brand new Persistent Volume (PV) and PVCβ€”directly inside your namespace that points straight back to the central shared disk.

It is a lightning-fast, zero-copy way to get instant read-only access to all the data you need. πŸš€

Shared Disk Pipeline

πŸ‘‰ Click here to trigger the Shared Disk Pipeline!