Conversation
- Rewrite install_envtest.sh to use official setup-envtest tool - Simplify test target: remove generate/manifests dependencies - Build targets still skip generate (CRDs already committed) - setup-envtest downloads from working sources, avoids HTTP 403 This enables integration tests to run in CI/CD.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix CI/CD build failures caused by envtest binary download issues
The build pipeline was failing because envtest binaries hosted on Google Cloud Storage
now return HTTP 403 (AccessDenied). This PR makes the build/test targets resilient to
this external dependency failure.
Changes:
generatedependency from build targets (CRDs already committed)Result: Builds and tests now pass in CI/CD without requiring external binary downloads.