Bug 1766066: Revert "Merge pull request #334 from danehans/bz_1758656" #388
Conversation
This reverts commit a858609, reversing changes made to 1eed813. We found in BZ https://bugzilla.redhat.com/show_bug.cgi?id=1762618 that at least some of our code, running on cluster, was accessing the external instead of internal api. While it is possible to make it work (by allowing your proxy to talk from internal to the apiserver) this is a change/regression from GA. Since we hit this with at least 1 part of our code we have decided to revert and try again with more testing.
openshift-ci-robot
added
the
bugzilla/invalid-bug
|
@eparis: This pull request references Bugzilla bug 1762618, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci-robot
added
the
size/S
eparis
changed the title
|
@eparis: This pull request references Bugzilla bug 1766066, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
eparis
added
bugzilla/valid-bug
|
manually overriding BZ check since this is a revert and the BZ in question is the long term fix... |
|
/lgtm |
|
/lgtm |
eparis
added
the
cherry-pick-approved
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danehans, eparis, pecameron, squeed The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
Bug 1770223: Reverts PR #388
This reverts commit a858609, reversing
changes made to 1eed813.
We found in BZ https://bugzilla.redhat.com/show_bug.cgi?id=1762618 that at least
some of our code, running on cluster, was accessing the external instead of internal
api.
While it is possible to make it work (by allowing your proxy to talk from internal
to the apiserver) this is a change/regression from GA. Since we hit this with at
least 1 part of our code we have decided to revert and try again with more testing.