Repository navigation
Conversation
Add an optional startupReadinessTimeoutSeconds field to OVNKubernetesConfig, behind the new TechPreview feature gate OVNKubernetesStartupReadinessTimeout. It sets how long ovnkube-node waits at startup for its gateway and management port to be created in OVN. When omitted, the platform default (currently 300 seconds) applies. Valid values are 1 to 3600. Enhancement: openshift/enhancements#2127
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (8)
📒 Files selected for processing (16)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughAdds the Suggested reviewers: Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to No actionable issue remains in the reviewed changes; the PR is mergeable after normal checks. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hello @cragr! Some important instructions when contributing to openshift/api: |
|
Hi @cragr. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
@JoelSpeed, could you review this API change? It also needs an |
|
The enhancement proposal needs an ack from the Networking team before this PR should be reviewed. |
|
/hold RFE needs discussion with the PM and engineering team before we move this forward |
Adds an optional
startupReadinessTimeoutSecondsfield toOVNKubernetesConfiginoperator.openshift.io/v1Network, behind a newOVNKubernetesStartupReadinessTimeoutfeature gate (DevPreviewNoUpgrade and TechPreviewNoUpgrade).It sets how long ovnkube-node waits at startup for its gateway and management port to be created in OVN. When omitted, the platform default applies (currently 300 seconds). Valid values are 1 to 3600 seconds. CNO will pass it to ovnkube-node as the
--startup-readiness-timeoutflag from ovn-kubernetes/ovn-kubernetes#7034.Enhancement: openshift/enhancements#2127
Tracking: OCPBUGS-127208
Changes:
features/features.go: new gateOVNKubernetesStartupReadinessTimeoutoperator/v1/types_network.go: new field,int32,+kubebuilder:validation:Minimum=1,+kubebuilder:validation:Maximum=3600operator/v1/tests/networks.operator.openshift.io/OVNKubernetesStartupReadinessTimeout.yaml: validation tests for unset, 600, 1, 3600, -1, 3601, update and removalmake update)Verification:
make update,make -C operator/v1 test(2074 passed, 0 failed), andmake lint(0 issues).AI-assisted: Claude Code (Claude Opus).