Bug 1993845
Summary: | Enabling internalTrafficPolicy=Local found two issues in test cases | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Martin Kennelly <mkennell> |
Component: | Networking | Assignee: | Martin Kennelly <mkennell> |
Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED UPSTREAM | Docs Contact: | |
Severity: | high | ||
Priority: | medium | CC: | danw |
Version: | 4.9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-08-31 08:14:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Kennelly
2021-08-16 09:19:15 UTC
For issue 1 - Either we increase pod privileges or up the port number above 1024. I went for the latter. I will disable the two test cases until upstream is resolved. fixes look good, though I'd add a comment to the code in the second one rather than only explaining in the commit message Can you push those PRs upstream and the link to the PRs from here so I'll see them? Then once it merges upstream you'll need to cherry-pick them into https://github.com/openshift/kubernetes, as explained in the README.openshift.md there (Though cherry-picking them is only relevant if we're actually planning to enable the alpha feature gate in 4.9, which I guess we probably aren't, so probably you don't actually have to do that.) Comment added to code. PRs: 1) Pod has insufficient privileges to bind to hostport 80. https://github.com/kubernetes/kubernetes/pull/104409 2) Comparison of FQDN and hostname fails https://github.com/kubernetes/kubernetes/pull/104408 Yes, but I may as well do this when it's merged so we have it done for the future. (In reply to Martin Kennelly from comment #4) > Yes, but I may as well do this when it's merged so we have it done for the > future. If we don't need the fix until OCP 4.10 then it doesn't have to be cherry-picked, because it will get pulled in as part of the rebase to kube 1.23. Dan, isn't OCP 4.9 based on k8 1.22 and therefore this feature is in beta? https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/ Therefore we need to cherry-pick back the fixes. Missing from this BZ was test case: "[sig-network] Services should respect internalTrafficPolicy=Local Pod (hostNetwork: true) to Pod [Feature:ServiceInternalTrafficPolicy]" This was also disabled due to upstream fix here: https://github.com/kubernetes/kubernetes/pull/104409/ ah, kube_features.go claims it's still alpha in the comment: // owner: @maplain @andrewsykim // kep: http://kep.k8s.io/2086 // alpha: v1.21 // // Enables node-local routing for Service internal traffic ServiceInternalTrafficPolicy featuregate.Feature = "ServiceInternalTrafficPolicy" but sets it to beta in defaultKubernetesFeatureGates: ServiceInternalTrafficPolicy: {Default: true, PreRelease: featuregate.Beta}, so it looks like they forgot to update the comment. So yes, it would be good to cherry-pick the fixes. (And maybe also fix the comment upstream to indicate its status correctly.) |