Merge pull request #6270 from EnterpriseDB/DOCS-776

Ironbank now supports EPAS operands

product_docs/docs/postgres_for_kubernetes/1/iron-bank.mdx

@@ -23,7 +23,7 @@ Iron Bank is a part of DoD's [Platform One](https://p1.dso.mil/).
 You will need your Iron Bank credentials to access the Iron Bank page for
 [EDB Postgres for Kubernetes](https://repo1.dso.mil/dsop/enterprisedb/edb-pg4k-operator).
 
-## Pulling the EDB PG4K image from Iron Bank
+## Pulling the EDB PG4K and operand images from Iron Bank
 
 The images are pulled from the separate [Iron Bank container registry](https://registry1.dso.mil/).
 To be able to pull images from the Iron Bank registry, please follow the
@@ -33,23 +33,28 @@ Specifically, you will need to use your
 [registry1](https://registry1.dso.mil/harbor/projects)
 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:
+To find the desired operator or operand images, we recommend to use the search tool to look
+with the string `enterprisedb`, and filter by `Tags`, looking for `stable`, as shown in
+the image. From there, you can get the instruction to pull the image:
 
 ![pulling-ironbank-images](./images/ironbank/pulling-the-image.png)
 
+For example, to pull the EPAS16 operand from Ironbank, you can run:
+
+```bash
+docker pull registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-16:16
+
+```
+
+If you want to pick a more specific tag or use a specific SHA, you need to find it from the [Harbor page](https://registry1.dso.mil/harbor/projects/3/repositories/enterprisedb%2Fedb-postgres-advanced-16/artifacts-tab).
+
 ## Installing the PG4K operator using the Iron Bank image
 
-For installation, you will need a deployment manifest that points to your Iron
-Bank image.
-You can take the deployment manifest from the
-[installation instructions for EDB PG4K](/postgres_for_kubernetes/latest/installation_upgrade/).
+For installation, you will need a deployment manifest that points to your Iron Bank image.
+You can take the deployment manifest from the [installation instructions for EDB PG4K](/postgres_for_kubernetes/latest/installation_upgrade/).
 For example, for the 1.22.0 release, the manifest is available at
-`https://get.enterprisedb.io/cnp/postgresql-operator-1.22.0.yaml`. \\
-There are a couple of places where you will need to set the image path for the
-IronBank image.
+`https://get.enterprisedb.io/cnp/postgresql-operator-1.22.0.yaml`.
+There are a couple of places where you will need to set the image path for the IronBank image.
 
 ```yaml
 apiVersion: apps/v1
@@ -90,3 +95,33 @@ 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](/postgres_for_kubernetes/latest/installation_upgrade/).
+
+## Deploying clusters with EPAS operands using IronBank images
+
+To deploy a cluster using the EPAS [operand](/postgres_for_kubernetes/latest/private_edb_registries/#operand-images) you must reference the Ironbank operand image appropriately in the `Cluster` resource YAML.
+For example, to deploy a PG4K Cluster using the EPAS 16 operand:
+
+1. Create or edit a `Cluster` resource YAML file with the following content:
+
+  ```yaml
+  apiVersion: postgresql.k8s.enterprisedb.io/v1
+  kind: Cluster
+  metadata:
+    name: cluster-example-full
+  spec:
+    imageName: registry1.dso.mil/ironbank/enterprisedb/edb-postgres-advanced-17:17
+    imagePullSecrets:
+      - name: my_ironbank_secret
+  ```
+
+2. Apply the YAML:
+
+  ```
+  kubectl apply -f <filename>
+  ```
+
+3. Verify the status of the resource:
+
+  ```
+  kubectl get clusters
+  ```