anandyadav3559 commented on code in PR #6642: URL: https://github.com/apache/camel-k/pull/6642#discussion_r3271968071
########## e2e/install/upgrade/upgrade_test.go: ########## Review Comment: Motivation: Right now we leverage the presence of the make target to perform installation of the older operator version during the upgrade E2E test. This forces the test to pull the entire GitHub project locally just to run the Makefile. We can instead install directly from the tag via a Kustomize procedure, which is faster and cleaner. Modifications: Removed the logic in e2e/install/upgrade/upgrade_test.go that creates a temporary directory, executes git clone, checks out the target tag, and runs make install-k8s-global. Replaced it with a temporary kustomization.yaml that dynamically applies the generated test namespace alongside the remote GitHub repository base (github.com/apache/camel-k/install/overlays/kubernetes/descoped?ref=v<lastVersion>). Executed installation using kubectl apply -k --server-side. Testing Verification: ✅ make fmt and make lint completed successfully with no issues. ⚠️ Note on Local testing with kind: While running the go test -v ./e2e/install/upgrade -tags=integration suite on a local kind cluster, the test initially timed out because the IntegrationPlatform resource failed to reach the Ready state. The operator logs showed: registry address not available, you need to set one. Because Camel K requires a container registry to push/pull integration images, and a local kind cluster does not provide one automatically, a local Docker registry had to be explicitly created and connected to the kind cluster for the upgrade tests to proceed and pass correctly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
