Add printer columns to PodNetworkConnectivityCheck CRD manifest - #2434
Add printer columns to PodNetworkConnectivityCheck CRD manifest#2434swshende-cmd wants to merge 2 commits into
Conversation
Companion change to openshift/api#2977 (now merged). The connectivity check controller applies this CRD manifest to the cluster at runtime. Without this update, the additionalPrinterColumns added in openshift/api would not take effect on cluster installs or upgrades. Adds four printer columns: Target Endpoint, Reachable, Since, and Age. Fixes: https://redhat.atlassian.net/browse/RFE-5093 Co-authored-by: Cursor <cursoragent@cursor.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (21)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe ChangesPodNetworkConnectivityCheck visibility
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This PR adds printer-column metadata so connectivity checks show target and status details in listings without changing controller logic or runtime behavior. No actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) Full details: Stable And Deterministic Test NamesExplanation PASS. The PR changes the CRD manifest, dependency metadata, and vendored generated files. It does not add or modify test files. No Ginkgo test declarations or dynamic test titles appear in the PR diff. The Full details: Test Structure And QualityExplanation PASS: The pull request changes only CRD YAML metadata, dependency files, and vendored openshift/api files. The diff against origin/master contains no Ginkgo test files or test code, so the single-responsibility, setup/cleanup, timeout, assertion-message, and test-pattern requirements do not apply. Full details: Microshift Test CompatibilityExplanation PASS — The pull request adds no Ginkgo e2e tests. The diff changes go.mod, go.sum, vendored OpenShift API files, and CRD manifests only. No changed test paths or added It, Describe, Context, When, IsMicroShiftCluster, or g.Skip usage exists. The MicroShift test compatibility check is therefore not applicable. Full details: Single Node Openshift (Sno) Test CompatibilityExplanation PASS: The pull request adds no Ginkgo tests or other test declarations. The base-to-tip diff changes CRD printer-column metadata, dependency files, and generated vendored OpenShift API files only. The SNO multi-node compatibility check is therefore not applicable. Full details: Topology-Aware Scheduling CompatibilityExplanation PASS: The pull request adds only four CRD Full details: Ote Binary Stdout ContractExplanation PASS — the PR changes CRD YAML, module metadata, and vendored OpenShift API declarations/generated manifests. No non-vendor Go source changed. AST and text searches found no changed Full details: Ipv6 And Disconnected Network Test CompatibilityExplanation PASS: The pull-request range changes the CRD manifest, dependency metadata, and vendored API files only. It adds or modifies no Ginkgo e2e tests and introduces no IPv4 or external-connectivity test requirement. Full details: No-Weak-CryptoExplanation PASS. The PR changes only CRD printer-column metadata, the openshift/api version and its vendored API declarations/generated files. The complete diff from origin/master adds no MD5, SHA-1, DES, 3DES, RC4, Blowfish, ECB, crypto imports, custom crypto, or secret/token comparisons. The changed Go additions are type declarations, generated deepcopy/OpenAPI code, and feature metadata. Full details: Container-PrivilegesExplanation PASS. The PR changes CRD printer-column metadata and dependency/vendor files. The added YAML contains no Full details: No-Sensitive-Data-In-LogsExplanation PASS: The pull request adds CRD printer-column metadata and synchronizes the vendored dependency. The changed Go files contain no added logging calls, and the only new runtime-visible value is the existing ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi @swshende-cmd. 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 Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain 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. |
|
@swshende-cmd: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/retest |
|
@swshende-cmd: Cannot trigger testing until a trusted user reviews the PR and leaves an 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-sigs/prow repository. |
|
@everettraven Hi, seems need /ok-to-test and approved |
|
@swshende-cmd It looks like there is a CI check failure that needs to be fixed. Additionally, I am not an approver in this repo so I cannot add the approved label here. @p0lyn0mial or @bertinatto may be able to help here. |
Updates the vendored openshift/api to include the printer columns added in openshift/api#2977 and syncs the CRD manifest used by the connectivity check controller. The verify job requires that the embedded manifest matches the vendored CRD exactly, so both the vendor bump and manifest sync are needed. Fixes: https://redhat.atlassian.net/browse/RFE-5093 Co-authored-by: Cursor <cursoragent@cursor.com>
|
New changes are detected. LGTM label has been removed. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: everettraven, swshende-cmd 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 |
|
Updated the PR to fix the CI
@p0lyn0mial @bertinatto Could you please add Thank you! |
Summary
additionalPrinterColumnsto the PodNetworkConnectivityCheck CRD manifest used by the connectivity check controlleropenshift/apiwould not be applied to clusters during install or upgrade since the controller stamps this manifest onto the clusterChange
Adds four printer columns to the CRD manifest at
pkg/operator/connectivitycheckcontroller/manifests/controlplane.operator.openshift.io_podnetworkconnectivitychecks.yaml:.spec.targetEndpoint.status.conditions[?(@.type=="Reachable")].status.status.conditions[?(@.type=="Reachable")].lastTransitionTime.metadata.creationTimestampContext
oc get podnetworkconnectivitycheckspreviously only showed NAME and AGE. With this change, users can see connectivity status at a glance:Fixes: https://redhat.atlassian.net/browse/RFE-5093
Test plan
Made with Cursor
Summary by CodeRabbit