fix: add squid proxy to E2E tasks for staging Developer Portal access#558
Closed
sampras343 wants to merge 1 commit into
Closed
fix: add squid proxy to E2E tasks for staging Developer Portal access#558sampras343 wants to merge 1 commit into
sampras343 wants to merge 1 commit into
Conversation
Configure HTTPS_PROXY/HTTP_PROXY pointing to squid.corp.redhat.com in the operator-e2e and sigstore-e2e task steps. This allows the openshift CLI strategy to fall back to the staging Developer Portal (developers.qa.redhat.com) when pre-release binaries are not yet published on production. NO_PROXY ensures cluster-internal traffic is not proxied. Implements SECURESIGN-2158 Signed-off-by: Sachin Sampras M <sampras343@gmail.com>
Member
Author
|
Closing due to RH proxy auto configuration files redirecting to specific URLs. Handling in securesign/sigstore-e2e#87 |
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.
Summary
HTTPS_PROXY/HTTP_PROXYenv vars tooperator-e2eandsigstore-e2eTekton tasks pointing tosquid.corp.redhat.com:3128NO_PROXYexcludes cluster-internal traffic (.cluster.local,.svc,quay.io, etc.)developers.qa.redhat.comwhen production binaries are not yet publishedContext
The operator's ConsoleCLIDownload manifests point to production
developers.redhat.com. During pre-release testing, binaries for the upcoming version (e.g., 1.5.0) are only available on the staging portal (developers.qa.redhat.com), which requires proxy access. The sigstore-e2e openshift strategy already has a prod→staging fallback (securesign/sigstore-e2e#83); this PR provides the network path to reach staging.Affected integration tests
Both
rhtas-operator-e2e-testandrhtas-operator-e2e-test-fipsare covered — they share the same pipeline (rhtas-operator-e2e.yaml) which references both updated tasks.Implements SECURESIGN-2158