doc updated for gitea and nginx change (#414)

* updated doc for haproxy change

* updated gitea tag/version uses

* updated tinkerbell-nginx to tinkerbell-haproxy

* updated doc

* Update on_prem_upgrade.rst

* Update on_prem_upgrade.rst

updated rke2 version

* Update on_prem_upgrade.rst

* Update on_prem_upgrade.rst

---------

Co-authored-by: PalashGoelIntel <palash.goel@intel.com>

Author: sunil-parida

docs/deployment_guide/on_prem_deployment/on_prem_deployment_profiles/on_prem_oxm_profile.rst

@@ -51,9 +51,9 @@ A sample network topology is presented in the diagram below:
 #. Most of Edge Orchestrator services are accessible via ``TRAEFIK_IP``, a Virtual IP reserved in the local subnet.
 
 #. The Edge Orchestrator must be configured with two more Virtual IPs that are reserved in the local subnet. ``ARGO_IP`` is used to access
-   ArgoCD server, while ``NGINX_IP`` exposes installation artifacts that are downloaded by Edge Nodes during OS provisioning.
+   ArgoCD server, while ``HAPROXY_IP`` exposes installation artifacts that are downloaded by Edge Nodes during OS provisioning.
 
-#. Note that one of ``TRAEFIK_IP``, ``NGINX_IP`` and ``ARGO_IP`` can be same as the physical interface's IP address (``ARGO_IP`` in the example).
+#. Note that one of ``TRAEFIK_IP``, ``HAPROXY_IP`` and ``ARGO_IP`` can be same as the physical interface's IP address (``ARGO_IP`` in the example).
 
 #. Only the PXE server is attached to the host networking and binds to the IP address of the physical network interface to listen to DHCP requests.
 
@@ -156,7 +156,7 @@ Post-installation steps
      .. code-block:: shell
 
         address=/[on.prem.domain.name]/[traefik-external-ip]
-        address=/tinkerbell-nginx.[on.prem.domain.name]/[ingress-nginx-external-ip]
+      address=/tinkerbell-haproxy.[on.prem.domain.name]/[ingress-nginx-external-ip]
 
 #. Retrieve the self-signed Edge Orchestrator certificate and install it to the trust store.
 

docs/deployment_guide/on_prem_deployment/on_prem_get_started/index.rst

@@ -85,7 +85,7 @@ Firewall Configuration
 The following table lists the network endpoints for Edge Orchestrator and edge nodes, which you can use to configure firewall rules tailored to your network environment.
 
 * ArgoCD Admin UI at ``argo.{domain}``. Intel recommends that you restrict the incoming traffic to a subset of known source IPs because this is an administrator interface.
-* BIOS Onboarding accesses ``tinkerbell-nginx.{domain}``.
+* BIOS Onboarding accesses ``tinkerbell-haproxy.{domain}``.
 * You can access all other services from edge nodes agents, UI, and APIs of Edge Orchestrator.
 
 .. list-table:: Network Endpoints for Edge Orchestrator and Edge Nodes
@@ -252,7 +252,7 @@ The following table lists the network endpoints for Edge Orchestrator and edge n
      -  443
      -  Edge infrastructure management
    * -  Edge node
-     -  tinkerbell-nginx.{domain}
+     -  tinkerbell-haproxy.{domain}
      -  TCP
      -  443
      -  BIOS onboarding

docs/deployment_guide/on_prem_deployment/on_prem_get_started/on_prem_install.rst

@@ -103,7 +103,10 @@ Core Deployment Configuration
      - ``registry-rs.edgeorchestration.intel.com``
    * - ``DEPLOY_VERSION``
      - Version of Edge Orchestrator to deploy
-     - ``v2025.2.0``
+     - ``v2026.0.0``
+   * - ``DEPLOY_REPO_BRANCH``
+     - Git tag or branch for deployment repository (overrides default commit)
+     - ``v2026.0.0``
    * - ``ORCH_INSTALLER_PROFILE``
      - Deployment profile for Edge Orchestrator
      - ``onprem``
@@ -144,8 +147,8 @@ Network Configuration
    * - ``TRAEFIK_IP``
      - MetalLB IP address for Traefik
      - (empty)
-   * - ``NGINX_IP``
-     - MetalLB IP address for NGINX
+   * - ``HAPROXY_IP``
+     - MetalLB IP address for HAProxy
      - (empty)
 
 Container Registry Configuration
@@ -787,7 +790,7 @@ An example of the `dnsmasq` config file:
    address=/vnc.[on.prem.domain.name]/[traefik-external-ip]
    address=/web-ui.[on.prem.domain.name]/[traefik-external-ip]
    address=/ws-app-service-proxy.[on.prem.domain.name]/[traefik-external-ip]
-   address=/tinkerbell-nginx.[on.prem.domain.name]/[ingress-nginx-external-ip]
+   address=/tinkerbell-haproxy.[on.prem.domain.name]/[ingress-nginx-external-ip]
    address=/mps.[on.prem.domain.name]/[traefik-external-ip]
    address=/rps.[on.prem.domain.name]/[traefik-external-ip]
    address=/mps-wss.[on.prem.domain.name]/[traefik-external-ip]

docs/deployment_guide/on_prem_deployment/on_prem_how_to/on_prem_upgrade.rst

@@ -1,23 +1,23 @@
 On-Prem Upgrade Guide
 =========================
 
-**Upgrade Path:** EMF On-Prem v3.1.3 → v2025.2.0
+**Upgrade Path:** EMF On-Prem v2025.2.0 → v2026.0.0
 
 **Document Version:** 1.0
 
 Overview
 --------
 
 This document provides step-by-step instructions to upgrade
-On-Prem Edge Manageability Framework (EMF) from version v3.1.3 to v2025.2.0.
+On-Prem Edge Manageability Framework (EMF) from version v2025.2.0 to  v2026.0.0
 
 Prerequisites
 -------------
 
 System Requirements
 ~~~~~~~~~~~~~~~~~~~
 
-- Current EMF On-Prem installation version 3.1.3 or later
+- Current EMF On-Prem installation version v2025.2.0 or later
 - Root/sudo privileges on orchestrator node
 - PostgreSQL service running and accessible
 - Sufficient disk space for backups (~200GB minimum)
@@ -53,7 +53,7 @@ Step 1: Download the Latest On-Prem Upgrade Script
     REGISTRY_URL='registry-rs.edgeorchestration.intel.com'
     RS_PATH='edge-orch/common/files/on-prem'
     ORAS_VERSION='1.1.0'
-    ORCH_VERSION='v2025.2.0'
+    ORCH_VERSION='v2026.0.0'
 
     # Install oras if not already installed
     if ! command -v oras &> /dev/null; then
@@ -135,7 +135,10 @@ Core Deployment Configuration
      - ``registry-rs.edgeorchestration.intel.com``
    * - ``DEPLOY_VERSION``
      - Version of Edge Orchestrator to deploy
-     - ``v2025.2.0``
+     - ``v2026.0.0``
+   * - ``DEPLOY_REPO_BRANCH``
+     - Git tag or branch for edge-manageability-framework deployment repository
+     - ``v2026.0.0``
    * - ``ORCH_INSTALLER_PROFILE``
      - Deployment profile for Edge Orchestrator
      - ``onprem``
@@ -176,10 +179,14 @@ Network Configuration
    * - ``TRAEFIK_IP``
      - MetalLB IP address for Traefik
      - (empty)
-   * - ``NGINX_IP``
-     - MetalLB IP address for NGINX
+   * - ``HAPROXY_IP``
+     - MetalLB IP address for HAProxy
      - (empty)
 
+.. note::
+   In **v2026.0.0 (latest release)**, the ingress controller was **replaced from NGINX to HAProxy**.
+   Please check whether the DNS entry for HAProxy is present after installation .
+
 Container Registry Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -335,6 +342,7 @@ Update the following sections:
 - **CORE DEPLOYMENT CONFIGURATION:**
   - RELEASE_SERVICE_URL
   - DEPLOY_VERSION
+  - DEPLOY_REPO_BRANCH
   - ORCH_INSTALLER_PROFILE
 
 - **AUTHENTICATION & SECURITY:**
@@ -343,7 +351,7 @@ Update the following sections:
 
 - **NETWORK CONFIGURATION:**
   - CLUSTER_DOMAIN
-  - ARGO_IP, TRAEFIK_IP, NGINX_IP
+  - ARGO_IP, TRAEFIK_IP, HAPROXY_IP
 
 - **CONTAINER REGISTRY:**
   - GITEA_IMAGE_REGISTRY
@@ -367,8 +375,10 @@ Update the following sections:
    kubectl get svc traefik -n orch-gateway
    kubectl get svc ingress-nginx-controller -n orch-boots
 
-   # Set deployment version (replace with your actual upgrade version tag)
-   export DEPLOY_VERSION=v2025.2.0
+  # Set deployment version (replace with your actual upgrade version tag)
+  export DEPLOY_VERSION=v2026.0.0
+  #Set the deploy repo release tag/branch (Gitea commit/tag/branch from EMF repo)
+  export DEPLOY_REPO_BRANCH=v2026.0.0
 
    # Set non-interactive mode to true to skip prompts
    export PROCEED=true
@@ -427,7 +437,7 @@ Before confirming in Terminal 1, open **Terminal 2** and update configurations:
       # Check current LoadBalancer IPs
       kubectl get svc argocd-server -n argocd
       kubectl get svc traefik -n orch-gateway
-      kubectl get svc ingress-nginx-controller -n orch-boots
+      kubectl get svc ingress-haproxy-kubernetes-ingress -n orch-boots
 
       # Verify LB IP configurations are updated
       nano repo_archives/tmp/edge-manageability-framework/orch-configs/clusters/onprem.yaml
@@ -451,7 +461,7 @@ Step 7: Monitor Upgrade Progress
 
 The upgrade process includes:
 
-- Upgrade RKE2 to 1.34.1 versions
+- Upgrade RKE2 to 1.34.4 versions
 - OS Configuration upgrade
 - Gitea upgrade
 - ArgoCD upgrade
@@ -575,8 +585,8 @@ Verify that the ``signed_ipxe.efi`` image is downloaded using the freshly downlo
       # Delete both files before downloading
       rm -rf Full_server.crt signed_ipxe.efi
       export CLUSTER_DOMAIN=cluster.onprem
-      wget https://tinkerbell-nginx.$CLUSTER_DOMAIN/tink-stack/keys/Full_server.crt --no-check-certificate --no-proxy -q -O Full_server.crt
-      wget --ca-certificate=Full_server.crt https://tinkerbell-nginx.$CLUSTER_DOMAIN/tink-stack/signed_ipxe.efi -q -O signed_ipxe.efi
+      wget https://tinkerbell-haproxy.$CLUSTER_DOMAIN/tink-stack/keys/Full_server.crt --no-check-certificate --no-proxy -q -O Full_server.crt
+      wget --ca-certificate=Full_server.crt https://tinkerbell-haproxy.$CLUSTER_DOMAIN/tink-stack/signed_ipxe.efi -q -O signed_ipxe.efi
 
    Once the above steps are successful, the orchestrator (Orch) is ready for onboarding new Edge Nodes (EN).
 

docs/shared/shared_gs_firewall_config.rst

@@ -5,7 +5,7 @@ The following table lists the network endpoints for Edge Orchestrator and edge n
 
 * ArgoCD Admin UI at ``argo.{domain}``. Intel recommends that you restrict the
   incoming traffic to a subset of known source IPs because this is an administrator interface.
-* BIOS Onboarding accesses ``tinkerbell-nginx.{domain}``.
+* BIOS Onboarding accesses ``tinkerbell-haproxy.{domain}``.
 * You can access all other services from edge nodes agents, UI, and APIs
   of Edge Orchestrator.
 
@@ -113,7 +113,7 @@ The following table lists the network endpoints for Edge Orchestrator and edge n
      -  TCP:443
      -  Cluster orchestration
    * -  Edge node
-     -  tinkerbell-nginx.{domain}
+     -  tinkerbell-haproxy.{domain}
      -  TCP:443
      -  BIOS onboarding
    * -  Edge Orchestrator admin

docs/user_guide/advanced_functionality/pxe_provisioning_with_cloud_emf.rst

@@ -57,7 +57,7 @@ Regardless of the deployment option, the first step is to download the iPXE scri
 
 .. code-block:: shell
 
-   wget https://tinkerbell-nginx.CLUSTER_FQDN/tink-stack/signed_ipxe.efi --no-check-certificate --no-proxy
+   wget https://tinkerbell-haproxy.CLUSTER_FQDN/tink-stack/signed_ipxe.efi --no-check-certificate --no-proxy
 
 .. note:: Replace CLUSTER_FQDN with the FQDN of the Edge Orchestrator.
 

docs/user_guide/set_up_edge_infra/edge_node_onboard/https_boot/https_boot_dell.rst

@@ -20,7 +20,7 @@ HTTPS boot is required to securely onboard devices.
 #. In iDRAC, go to **Configuration** > **BIOS Settings** > **Network Settings**.
 #. Set **HTTP Device1** to **Enabled**.
 #. Go to **HTTP Device1 Settings** > **Interface** and choose the NIC identified previously.
-#. Set the **URI** to ``https://tinkerbell-nginx.CLUSTER_FQDN/tink-stack/signed_ipxe.efi``
+#. Set the **URI** to ``https://tinkerbell-haproxy.CLUSTER_FQDN/tink-stack/signed_ipxe.efi``
    path. This value is defined during installation of |software_prod_name|.
 
    .. note:: Replace CLUSTER_FQDN with the name of the domain of the Edge Orchestrator.

docs/user_guide/set_up_edge_infra/edge_node_onboard/https_boot/https_boot_lenovo.rst

@@ -13,15 +13,15 @@ Prepare the ISO image one time, so that it will be mounted as Virtual Media on t
 
    .. code-block:: shell
 
-      wget https://tinkerbell-nginx.${CLUSTER_FQDN}/tink-stack/keys/Full_server.crt --no-check-certificate --no-proxy
+      wget https://tinkerbell-haproxy.${CLUSTER_FQDN}/tink-stack/keys/Full_server.crt --no-check-certificate --no-proxy
 
 #. Use the following command to download the secure boot certificate for iPXE and Hook Os, independent of final OS.
    This is step is not required if **Secure Boot** is not enabled.
    Replace CLUSTER_FQDN with the name of the domain that is used during installation.
 
    .. code-block:: shell
 
-      wget https://tinkerbell-nginx.${CLUSTER_FQDN}/tink-stack/keys/db.der --no-check-certificate --no-proxy
+      wget https://tinkerbell-haproxy.${CLUSTER_FQDN}/tink-stack/keys/db.der --no-check-certificate --no-proxy
 
    For Edge Microvisor Toolkit, if Secure Boot (SB) is enabled (Not required for Ubuntu):
 
@@ -142,7 +142,7 @@ HTTP Boot Option
       :alt: Boot Option
       :width: 750px
 
-#. Set **Boot URI** to ``https://tinkerbell-nginx.CLUSTER_FQDN/tink-stack/signed_ipxe.efi``. This value is defined during installation of |software_prod_name|\ .
+#. Set **Boot URI** to ``https://tinkerbell-haproxy.CLUSTER_FQDN/tink-stack/signed_ipxe.efi``. This value is defined during installation of |software_prod_name|\ .
 
    .. note:: Replace CLUSTER_FQDN with the domain name of |software_prod_name|\ .
 

docs/user_guide/set_up_edge_infra/edge_node_onboard/https_boot/index.rst

@@ -19,7 +19,7 @@ Requirements
 HTTPS-assisted boot flow
 ------------------------
 
-#. Configure BIOS with UEFI HTTP URL pointing to ``https://tinkerbell-nginx.CLUSTER_FQDN/tink-stack/signed_ipxe.efi``.
+.#. Configure BIOS with UEFI HTTP URL pointing to ``https://tinkerbell-haproxy.CLUSTER_FQDN/tink-stack/signed_ipxe.efi``.
 
 #. Optionally, if Edge Nodes have been configured with Secure Boot, configure BIOS to enable Secure Boot and upload |software_prod_name| CA certificates.
 

docs/user_guide/set_up_edge_infra/edge_node_onboard/prerequisites/racadm_on_linux.rst

@@ -32,7 +32,7 @@ Install RACADM on Linux PC
       NODE_BMC_PWD="Your iDRAC password"
 
       CLUSTER_FQDN="Your cluster FQDN established when deploying Edge Orchestrator"
-      TINK_FQDN=tinkerbell-nginx.${CLUSTER_FQDN}
+      TINK_FQDN=tinkerbell-haproxy.${CLUSTER_FQDN}
 
       # RACADM login
       LOGIN="-r ${NODE_BMC_IP} -u ${NODE_BMC_USER} -p ${NODE_BMC_PWD} --nocertwarn"