Adding Proxy Configuration for private clusters #132
Closed
Conversation
This file contains 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
paigerube14
commented
Nov 21, 2024
src/testdata/namespace_template.j2
Outdated
| labels: | ||
| kubernetes.io/metadata.name: {{name}} |
There was a problem hiding this comment.
needed to run tests on openshift cluster
|
@tsebastiani are you able to take a look at why these tests might be failing? I made a kind cluster and ran the tests locally and haven't hit the same issues |
paigerube14
force-pushed
the
proxy
branch
3 times, most recently
from
1dcfb3c to
7530bde
Compare
Signed-off-by: Paige Patton <prubenda@redhat.com>
|
closing in favor of pr: #140 That pr edits the test order and has consistent tests passing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Certain configurations of openshift are behind a
http_proxyenvironment variable. This will allow us to run tests on these clustersI found though this only works for scenarios that are imbedded into krkn. the Native scenarios each have their own api configuration. Need to see if that's still necessary. Also pod scenarios are effected by this