Iron Bank v1
Iron Bank is the DoD's source for hardened containers.
[… snipped …]
Iron Bank ultimately is for anyone to consume or contribute. However, we specifically target the following personas:
- DoD organizations wishing to consume hardened containers and Iron Banks BoE (Body of Evidence) for each container
- DoD organizations wishing to help contribute to containers (e.g. bug fixes, new applications, updates)
- DoD Authorization Officials wishing to understand the risks associated with applications
- Commercial vendors wishing to bring their application to the DoD
Iron Bank is a part of DoD's Platform One.
You will need your Iron Bank credentials to access the Iron Bank page for EDB Postgres for Kubernetes.
Specifically, you will need to use your registry1 credentials to pull images.
To find the desired operator image, we recommend to use the search tool to look
with the string
edb, and filter by
Tags, looking for
stable, as shown in
the image. From there, you can get the instruction to pull the image, for
example using Docker:
For installation, you will need a deployment manifest that points to your Iron
You can take the deployment manifest from the
installation instructions for EDB PG4K.
For example, for the 1.22.0 release, the manifest is available at
There are a couple of places where you will need to set the image path for the
If you wish for the operator to be deployed from Iron Bank directly, you will need to create and set the pull secret with the credentials to the registry, as described above.
It may be easier to get the image from Iron Bank with the instructions on the site, and from there, re-tag and publish it to a local registry, or push it directly to your Kubernetes nodes.
Once you have this in place, you can apply your manifest normally with
kubectl apply -f, as described in the installation instructions.