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
validate configuration of kube-proxy IPVS tcp,tcpfin,udp timeout #88657
validate configuration of kube-proxy IPVS tcp,tcpfin,udp timeout #88657
Conversation
Hi @chendotjs. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
e677e2e
to
71c8819
Compare
/assign @lbernail @andrewsykim |
@@ -283,6 +284,24 @@ func validateKubeProxyNodePortAddress(nodePortAddresses []string, fldPath *field | |||
return allErrs | |||
} | |||
|
|||
func validateIPVSTimeout(config kubeproxyconfig.KubeProxyIPVSConfiguration, fldPath *field.Path) field.ErrorList { |
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.
do we need to move it to an independent function?
Seems that the conntrack timeouts are validated in the same function
config.TCPCloseWaitTimeout.Duration
config.TCPEstablishedTimeout.Duration
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.
I think it makes to have a function for this given the current way we validate the ipvs configuration
/ok-to-test |
allErrs := field.ErrorList{} | ||
|
||
if config.TCPTimeout.Duration < 0 { | ||
allErrs = append(allErrs, field.Invalid(fldPath.Child("TCPTimeout"), config.MinSyncPeriod, "must be greater than or equal to 0")) |
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.
config.MinSyncPeriod -> config.TCPTimeout
} | ||
|
||
if config.TCPFinTimeout.Duration < 0 { | ||
allErrs = append(allErrs, field.Invalid(fldPath.Child("TCPFinTimeout"), config.MinSyncPeriod, "must be greater than or equal to 0")) |
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.
config.MinSyncPeriod -> config.TCPFinTimeout
} | ||
|
||
if config.UDPTimeout.Duration < 0 { | ||
allErrs = append(allErrs, field.Invalid(fldPath.Child("UDPTimeout"), config.MinSyncPeriod, "must be greater than or equal to 0")) |
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.
config.MinSyncPeriod -> config.UDPTimeout
Thanks @chendotjs ! |
71c8819
to
e79f49e
Compare
Thanks @aojea for review. |
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.
/lgtm
/priority important-soon
/assign @thockin
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.
Thanks!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chendotjs, thockin 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
kube-proxy should validate --ipvs-tcp-timeout, --ipvs-tcpfin-timeout, --ipvs-udp-timeout flag values at start.
Which issue(s) this PR fixes:
Fixes #88656
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: