-
Notifications
You must be signed in to change notification settings - Fork 298
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
OCPBUGS-33237: Run haproxy to connect to kas from data plane if noproxy settings contain kas #3999
Conversation
@enxebre: This pull request references Jira Issue OCPBUGS-33237, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
/hold |
/jira refresh |
@enxebre: This pull request references Jira Issue OCPBUGS-33237, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request. 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre 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 |
for _, substr := range substrings { | ||
if strings.Contains(s, substr) { | ||
return true | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The apiServerAddr can be an IP and spec.configuration.proxy.noProxy
(ProxySpec) could be a CIDR/IP so that may need to be checked as well.
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
d4dfca4
to
7b1327d
Compare
} | ||
|
||
machineConfig := manifests.MachineConfigAPIServerHAProxy() | ||
ignition.SetMachineConfigLabels(machineConfig) | ||
serializedConfig, err := apiServerProxyConfig(haProxyImage, controlPlaneOperatorImage, apiServerExternalAddress, apiServerInternalAddress, apiServerExternalPort, apiServerInternalPort, apiserverProxy) | ||
serializedConfig, err := apiServerProxyConfig(haProxyImage, controlPlaneOperatorImage, apiServerExternalAddress, apiServerInternalAddress, apiServerExternalPort, apiServerInternalPort, apiserverProxy, noProxy, hcluster.Spec.Networking.ServiceNetwork[0].CIDR.String(), hcluster.Spec.Networking.ClusterNetwork[0].CIDR.String()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where are we checking that hcluster.Spec.Networking.ServiceNetwork
is not zero-length?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is defaulted in the API, I can still add a safety check
if proxyAddr == "" { | ||
|
||
// Check if no proxy contains any address that should result in skipping the system proxy | ||
containsSubstring := func(s string, substrings ...string) bool { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use slices.ContainsFunc()
?
@@ -0,0 +1 @@ | |||
zz_fixture_TestAPIServerHAProxyConfig.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something went wrong here, should be serializing the config as YAML
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
they are syslinks and I think that's how GH represent the change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did they get generated from UPDATE=true go test ./...
? I never saw symlinked fixtures before
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nvm symlink was causing troubles so I recreated then with test
b7a6c03
to
909d70f
Compare
Without this change, even if the kas is contained in no_proxy config we would deploy the adhoc kubernetes-default-proxy which would forward connections targetting kas pod through the proxy.
/test e2e-aws |
/retest |
/lgtm |
/hold cancel |
/test e2e-azure |
@enxebre: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
905708a
into
openshift:main
@enxebre: Jira Issue OCPBUGS-33237: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-33237 has been moved to the MODIFIED state. 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 openshift-eng/jira-lifecycle-plugin repository. |
/cherry-pick release-4.15 |
@celebdor: new pull request created: #4014 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-sigs/prow repository. |
Fix included in accepted release 4.16.0-0.nightly-2024-05-14-095225 |
Without this change, even if the kas is contained in no_proxy config we would deploy the adhoc kubernetes-default-proxy which would forward connections targetting kas pod through the proxy.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist