Merge pull request #6200 from EnterpriseDB/docs/pg4k/edbprivaterepos

First pass of changes for license-key free installation

Author: djw-m

product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx

@@ -14,6 +14,39 @@ originalFilePath: 'src/installation_upgrade.md'
 
 ## Installation on Kubernetes
 
+### Obtaining an EDB subscription token
+
+!!! Important
+    You must obtain an EDB subscription token to install EDB Postgres for Kubernetes. Without a token, you will not be able to access the EDB private software repositories.
+
+Installing EDB Postgres for Kubernetes requires an EDB Repos 2.0 token to gain access to the EDB private software repositories.
+
+You can obtain the token by visiting your [EDB Account Profile](https://www.enterprisedb.com/accounts/profile). You will have to sign in if you are not already logged in.
+
+Your account profile page displays the token to use next to **Repos 2.0 Token** label. By default, the token is obscured, click the "Show" button (an eye icon) to reveal it.
+
+Your token entitles you to access one of two repositories: standard or enterprise.
+
+* `standard` - Includes the operator and the EDB Postgres Extended operand images.
+* `enterprise` - Includes the operator and the EDB Postgres Advanced and EDB Postgres Extended operand images.
+
+Set the relevant value, determined by your subscription, as an environment variable `EDB_SUBSCRIPTION_PLAN`.
+
+```shell
+EDB_SUBSCRIPTION_PLAN=enterprise
+```
+
+then set the Repos 2.0 token to an environment variable `EDB_SUBSCRIPTION_TOKEN`.
+
+```shell
+EDB_SUBSCRIPTION_TOKEN=<your-token>
+```
+
+!!! Warning
+    The token is sensitive information. Please ensure that you don't expose it to unauthorized users.
+
+You can now proceed with the installation.
+
 ### Using the Helm Chart
 
 The operator can be installed using the provided [Helm chart](https://github.com/EnterpriseDB/edb-postgres-for-kubernetes-charts).
@@ -23,12 +56,43 @@ The operator can be installed using the provided [Helm chart](https://github.com
 The operator can be installed like any other resource in Kubernetes,
 through a YAML manifest applied via `kubectl`.
 
+#### Install the EDB pull secret
+
+Before installing EDB Postgres for Kubernetes, you need to create a pull secret for EDB software in the `postgresql-operator-system` namespace.
+
+
+The pull secret needs to be saved in the namespace where the operator will reside. Create the `postgresql-operator-system` namespace using this command:
+
+```shell
+kubectl create namespace postgresql-operator-system
+```
+
+To create the pull secret itself, run the following command:
+
+```shell
+kubectl create secret -n postgresql-operator-system docker-registry edb-pull-secret \
+  --docker-server=docker.enterprisedb.com \
+  --docker-username=k8s_$EDB_SUBSCRIPTION_PLAN \
+  --docker-password=$EDB_SUBSCRIPTION_TOKEN
+```
+
+#### Install the operator
+
+Now that the pull-secret has been added to the namespace, the operator can be installed like any other resource in Kubernetes,
+through a YAML manifest applied via `kubectl`. 
+
+There are two different manifests available depending on your subscription plan:
+
+- Standard: The [latest standard operator manifest](https://get.enterprisedb.io/pg4k/pg4k-standard-1.24.1.yaml).
+- Enterprise: The [latest enterprise operator manifest](https://get.enterprisedb.io/pg4k/pg4k-enterprise-1.24.1.yaml).
+
+You can install the manifest for the latest version of the operator by running:
 You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.24.1.yaml)
 for this minor release as follows:
 
 ```sh
 kubectl apply --server-side -f \
-  https://get.enterprisedb.io/cnp/postgresql-operator-1.24.1.yaml
+   https://get.enterprisedb.io/pg4k/pg4k-$EDB_SUBSCRIPTION_PLAN-1.24.1.yaml
 ```
 
 You can verify that with:
@@ -72,9 +136,8 @@ for a more comprehensive example.
 In Kubernetes, the operator is by default installed in the `postgresql-operator-system`
 namespace as a Kubernetes `Deployment`. The name of this deployment
 depends on the installation method.
-When installed through the manifest or the `cnp` plugin, it is called
-`postgresql-operator-controller-manager` by default. When installed via Helm, the default name
-is `postgresql-operator-cloudnative-pg`.
+When installed through the manifest or the `cnp` plugin, by default, it is called `postgresql-operator-controller-manager`.
+When installed via Helm, by default, the deployment name is derived from the helm release name, appended with the suffix `-edb-postgres-for-kubernetes` (e.g., `<name>-edb-postgres-for-kubernetes`).
 
 !!! Note
     With Helm you can customize the name of the deployment via the