-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1744532: proxy: add .svc and .cluster.local to default noProxy #2257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Antonio Murdaca <runcom@linux.com>
|
/retest |
|
This list still differs from the list in cluster-network-operator, do they need to be exactly the same? |
|
So from investigating that bug linked I noticed that those two were the hostnames missing, can't speak for the other differences between the lists but if they differs between bootstrap and in-cluster the MCO cannot proceed. |
|
Another question would be why this is only noticed on vsphere upi and not on aws ipi - not knowledgeable enough for that |
|
Ok, I agree those should be added here. Just seemed like you were suggesting the lists needed to be identical to avoid problems. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: runcom, sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
so I'm not entirely sure about the list being identical :) just from debugging, |
|
@runcom: This pull request references Bugzilla bug 1744532, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
So how do we ratchet future adjustments in without breaking anything? Ideally the installer-generated defaults would just be enough for the installer to be able to reach the registry to pull the release image and dependencies. Then we'd run the networking operator to (re-)render the manifest before pushing into the cluster to stay in sync? |
so, one of the mystery here is that, apparently, this only happened on vsphere and hasn't happened on aws api so I think our current CI should have caught this just fine.
we could do this yeah, right now, the installer has to keep up with networking operator changes as we've spotted here. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@runcom: All pull requests linked via external trackers have merged. Bugzilla bug 1744532 has been moved to the MODIFIED state. DetailsIn 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. |
Proxy controller (I think) changed this openshift/cluster-network-operator#295 but the installer isn't doing the same. This is causing a different proxy config being generated between bootstrap and in-cluster which in turn causes the MCO to generates different machineconfigs and resulting in https://bugzilla.redhat.com/show_bug.cgi?id=1744532#c13
Signed-off-by: Antonio Murdaca runcom@linux.com