Docs: Update enterprise installation licensing docs (#9313)

* Docs: Update enterprise installation licensing docs

* CR Fixes

Author: N-o-Z

docs/src/enterprise/getstarted/install.md

@@ -225,6 +225,41 @@ Error: feature not licensed - to enable, contact support@treeverse.io
 
 ---
 
+### License Configuration
+
+!!! note 
+    You can proceed without this step at the moment. However, licensing enforcement will be introduced soon. 
+    Contact [support](mailto:support@treeverse.io) to receive your installation license.
+
+lakeFS Enterprise requires a valid license to work.
+In the helm chart the license is provided as a JWT token either from an existing secret or explicitly.
+The following demonstrates how to configure the license in the `values` file:
+
+=== "License with token provided in secrets"
+
+    ```yaml
+    enterprise:
+      enabled: true
+
+    secrets:
+        licenseContents: <Your licese JWT token>
+    ```
+
+=== "License with token provided from existing secret"
+
+    ```yaml
+    enterprise:
+      enabled: true
+
+    # Name of existing secret to use
+    existingSecret: <Name of existing secret>
+
+    secretKeys:
+      # Use to fetch license token from an existing secret:
+       licenseContentsKey: <Name of license contents key from existing secret>
+    ```
+
+
 ### Authentication Configuration
 
 Authentication in lakeFS Enterprise is handled directly by the lakeFS Enterprise service. This section explains the configurations required for setting up SSO.

docs/src/enterprise/getstarted/quickstart.md

@@ -43,7 +43,7 @@ Checkout the [RBAC demo](https://github.com/treeverse/lakeFS-samples/blob/main/0
 3. With the token you've been granted, login locally to Docker Hub with `docker login -u externallakefs -p <TOKEN>`.
 
 <br>
-The quickstart docker-compose files below create a lakeFS server that's connected to a [local blockstore](../../howto/deploy/onprem.md#local-blockstore) and spin up the following containers:
+The quickstart docker-compose file below creates a lakeFS server that's connected to a [local blockstore](../../howto/deploy/onprem.md#local-blockstore) and spin up the following containers:
 
 * lakeFS Enterprise
 * Postgres: used by lakeFS as a KV store

docs/src/enterprise/upgrade.md

@@ -34,7 +34,6 @@ To migrate from fluffy to lakeFS Enterprise, follow the steps below:
 
 ## Configuration Changes
 
-
 ### Authentication configuration
 
 Most Fluffy `auth.*` settings migrate directly to lakeFS Enterprise with the same structure. Below are the differences between the configurations.
@@ -363,6 +362,40 @@ image:
 
 **Note**: If you're not overriding the image, the chart will automatically use the correct Enterprise image.
 
+#### Step 3.5: License Configuration
+
+!!! note
+    You can proceed without this step at the moment. However, licensing enforcement will be introduced soon.
+    Contact [support](mailto:support@treeverse.io) to receive your installation license.
+
+lakeFS Enterprise requires a valid license to work.
+In the helm chart the license is provided as a JWT token either from an existing secret or explicitly.
+The following demonstrates how to configure the license in the `values` file:
+
+=== "License with token provided in secrets"
+
+    ```yaml
+    enterprise:
+      enabled: true
+
+    secrets:
+        licenseContents: <Your licese JWT token>
+    ```
+
+=== "License with token provided from existing secret"
+
+    ```yaml
+    enterprise:
+      enabled: true
+
+    # Name of existing secret to use
+    existingSecret: <Name of existing secret>
+
+    secretKeys:
+        # Use to fetch license token from an existing secret:
+        licenseContentsKey: <Name of license contents key from existing secret>
+    ```
+
 #### Step 4: Migrate Your Authentication Configuration
 
 Using the [configuration examples below](#configuration-examples), update your values.yaml file: