Updated documentation per task request

Updates documentation to clear up how to handle IPS.

Closes #686 (closed)

docs/developer/develop-package.md

@@ -169,3 +169,27 @@ Under Settings → Repository → Default Branch, ensure that main is selected.
 
 1. After the merge create a git tag following the charter convention of {UpstreamChartVersion}-bb.{BigBangVersion}. The tag should exactly match the chart version in the Chart.yaml.
 example:    1.2.3-bb.0
+
+### Private registry secret creation
+In some instances you may wish to manually create a private-registry secret in the namespace or during a helm deployment.  There are a couple of ways to do this:
+
+1. The first way is to add the secret manually using kubectl. This method is useful for standalone package testing/development.
+
+   ```shell
+   kubectl create secret docker-registry private-registry --docker-server="https://registry1.dso.mil" --docker-username='Username' --docker-password="CLI secret" --docker-email=<your-email> --namespace=<package-namespace>
+   ```
+2. The second is to create a yaml file containing the secret and apply it during a helm install. This method is applicable when installing your new package as part of the Big Bang chart. In this example the file name is "reg-creds.yaml":
+
+Create the file with the secret contents:
+   ```yaml
+   registryCredentials:
+     registry: registry1.dso.mil
+     username: ""
+     password: ""
+     email: ""
+   ```
+
+Then include a reference to your file during your helm install command by adding the below `-f` to your Big Bang install command:
+   ```shell
+   -f reg-creds.yaml
+   ```
\ No newline at end of file