Fix forward-compatibility workflow e2e failures

Several issues prevented the forward-compatibility workflow from
running successfully:

- Add permissions (contents:read, id-token:write) to run-e2e-tests
  job, required by the reusable e2e-tests workflow.

- Fix mig-manager GitHub repo name: the image is published from
  NVIDIA/mig-parted, not NVIDIA/k8s-mig-manager (which doesn't
  exist).

- Replace yq-based YAML merging with Helm's native multi-file
  support (-f file1 -f file2). The remote test machines don't have
  yq installed.

- Pass OPERATOR_OPTIONS through in the values-file install path so
  test-case-specific flags (e.g. driver.nvidiaDriverCRD.enabled)
  are not silently dropped.

Signed-off-by: Rajath Agasthya <ragasthya@nvidia.com>

Author: rajathagasthya

.github/scripts/get-latest-images.sh

@@ -32,15 +32,15 @@ fi
 case "${COMPONENT}" in
     toolkit)
         IMAGE_REPO="ghcr.io/nvidia/container-toolkit"
-        GITHUB_REPO="NVIDIA/container-toolkit"
+        GITHUB_REPO="NVIDIA/nvidia-container-toolkit"
         ;;
     device-plugin)
         IMAGE_REPO="ghcr.io/nvidia/k8s-device-plugin"
         GITHUB_REPO="NVIDIA/k8s-device-plugin"
         ;;
     mig-manager)
         IMAGE_REPO="ghcr.io/nvidia/k8s-mig-manager"
-        GITHUB_REPO="NVIDIA/k8s-mig-manager"
+        GITHUB_REPO="NVIDIA/mig-parted"
         ;;
     *)
         echo "Error: Unknown component '${COMPONENT}'" >&2

.github/workflows/forward-compatibility.yaml

@@ -69,6 +69,9 @@ jobs:
 
   run-e2e-tests:
     needs: [fetch-latest-images]
+    permissions:
+      contents: read
+      id-token: write
     uses: ./.github/workflows/e2e-tests.yaml
     with:
       operator_image: ghcr.io/nvidia/gpu-operator

tests/scripts/install-operator.sh

@@ -34,30 +34,26 @@ if [[ "${USE_VALUES_FILE}" == "true" ]]; then
 	# Generate a temporary values file from environment variables
 	# and merge it with the provided VALUES_FILE
 	TEMP_ENV_VALUES=$(mktemp)
-	trap 'rm -f "${TEMP_ENV_VALUES:-}" "${COMBINED_VALUES:-}"' EXIT
+	trap 'rm -f "${TEMP_ENV_VALUES:-}"' EXIT
 	${SCRIPT_DIR}/env-to-values.sh "${TEMP_ENV_VALUES}"
 
-	# If VALUES_FILE exists, merge it with env-generated values using yq
-	# Otherwise just use the env-generated values
+	# If VALUES_FILE exists, use both files with Helm's native multi-file
+	# support (-f). Helm merges values in order, with later files taking
+	# precedence — so env-generated values override the provided file.
 	if [[ -f "${VALUES_FILE}" ]]; then
 		echo ""
 		echo "Using provided values file: ${VALUES_FILE}"
 		cat "${VALUES_FILE}"
 		echo ""
-		echo "Merged with environment-based values:"
+		echo "Environment-based values (takes precedence):"
 		cat "${TEMP_ENV_VALUES}"
 
-		# Create a combined values file using yq for proper YAML merging
-		COMBINED_VALUES=$(mktemp)
-		if ! command -v yq >/dev/null 2>&1; then
-			echo "Error: yq is required to merge YAML values files but was not found in PATH." >&2
-			echo "Install yq: https://github.com/mikefarah/yq" >&2
-			exit 1
-		fi
-		# yq merges YAML properly, with later files taking precedence
-		yq ea '. as $item ireduce ({}; . * $item )' "${VALUES_FILE}" "${TEMP_ENV_VALUES}" > "${COMBINED_VALUES}"
-		VALUES_FILE="${COMBINED_VALUES}"
+		# Pass both files to helm; the env values file comes second
+		# so its values take precedence over the override file.
+		EXTRA_VALUES_FILES="-f ${VALUES_FILE}"
+		VALUES_FILE="${TEMP_ENV_VALUES}"
 	else
+		EXTRA_VALUES_FILES=""
 		VALUES_FILE="${TEMP_ENV_VALUES}"
 	fi
 
@@ -113,7 +109,9 @@ if [[ "${USE_VALUES_FILE}" == "true" ]]; then
 	echo "Using values file approach: ${VALUES_FILE}"
 	${HELM} install ${PROJECT_DIR}/deployments/gpu-operator --generate-name \
 		-n "${TEST_NAMESPACE}" \
+		${EXTRA_VALUES_FILES} \
 		-f "${VALUES_FILE}" \
+		${OPERATOR_OPTIONS} \
 		--wait
 else
 	echo "Using --set flags approach"