NO-ISSUE: Update github.com/openshift/api digest to 26dbe2a#748
NO-ISSUE: Update github.com/openshift/api digest to 26dbe2a#748red-hat-konflux[bot] wants to merge 1 commit intomasterfrom
Conversation
|
@red-hat-konflux[bot]: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughUpdated the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: red-hat-konflux[bot] 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 |
|
Hi @red-hat-konflux[bot]. Thanks for your PR. I'm waiting for a github.com 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. 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. |
4977d85 to
0648219
Compare
0648219 to
d27fe82
Compare
d27fe82 to
b74aead
Compare
b74aead to
264c8c2
Compare
264c8c2 to
c60c8c7
Compare
58984fc to
c60c8c7
Compare
832163d to
c87d482
Compare
c87d482 to
865991a
Compare
a395869 to
25b1583
Compare
25b1583 to
865816b
Compare
865816b to
5afe6a8
Compare
5afe6a8 to
b9dc5a9
Compare
b9dc5a9 to
09b94c9
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@api/go.mod`:
- Line 6: The PR title's referenced digest (71e91db) doesn't match the actual
pseudo-version digest in api/go.mod (618697272d69); update the PR title or
description to reflect the true dependency change, or revert/api-modify the
go.mod entry to the intended pseudo-version so they match; locate the dependency
line with "github.com/openshift/api v0.0.0-20260203111218-618697272d69" and
ensure the PR metadata uses the same digest string to avoid confusion.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@api/go.mod`:
- Line 6: Search the codebase for references to the removed OpenShift feature
gate symbols (e.g., VolumeAttributesClass, ProcMountType) and any SDN-related
feature gate constants; if found (likely via imports from
github.com/openshift/api), update those call sites to either use the equivalent
string names or guarded logic (e.g., replace usages of the exported constants
FeatureGateVolumeAttributesClass/FeatureGateProcMountType with their literal
feature gate names or conditional runtime checks), or else pin the go.mod
dependency back to the older github.com/openshift/api version; make the change
in the functions/modules that import these symbols (replace constant references
or add compatibility wrappers) so the build no longer depends on the removed
exported symbols.
api/go.mod
Outdated
|
|
||
| require ( | ||
| github.com/openshift/api v0.0.0-20240830023148-b7d0481c9094 | ||
| github.com/openshift/api v0.0.0-20260206223843-639b501bb529 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check the openshift/api repository details and tags between the versions
git ls-files api/go.modRepository: openshift/cluster-api-provider-agent
Length of output: 90
🌐 Web query:
github.com/openshift/api v0.0.0-20260206223843 breaking changes
💡 Result:
Your version string is incomplete: a Go pseudo-version should look like v0.0.0-20260206223843-<12+ char commit> (the trailing commit hash is what uniquely identifies the code). With just v0.0.0-20260206223843 I can’t deterministically map it to one commit.
That said, on/around Feb 6, 2026, openshift/api landed these likely breaking changes (compile-time / API surface changes for Go consumers):
- Removed FeatureGate
VolumeAttributesClass(including the exported Go symbolFeatureGateVolumeAttributesClassand related featuregate payload entries). This can break builds if you referenced that constant or expected it in generated featuregate manifests. [1] - Removed FeatureGate
ProcMountType(including the exported Go symbolFeatureGateProcMountTypeand related payload entries). Same type of build/config break as above. [2] - Removed/graduated SDN-related feature gates (“Remove graduated SDN feature gates”), which also touched networking API validation annotations and generated manifests. If you referenced any of the removed feature-gate names/symbols (or relied on those gates gating validation), this can be breaking. [3]
Non-breaking (additive) change on Feb 6:
- Added FeatureGate
DRAPartitionableDevices(new symbol/manifests). [4]
If you paste the full pseudo-version (including the -<commit> suffix), I can give the exact breaking-change list for that commit and the diff vs the previous version you were on.
Sources:
[1] openshift/api commit removing VolumeAttributesClass FeatureGate: (github.com)
[2] openshift/api commit removing ProcMountType: (github.com)
[3] openshift/api commit removing graduated SDN feature gates: (github.com)
[4] openshift/api commit adding DRAPartitionableDevices: (github.com)
Citations:
🌐 Web query:
openshift/api security advisory CVE 2025 2026
💡 Result:
OpenShift “API” security advisories / CVEs (2025–2026) — what to look at
Notable OpenShift API-server CVE in 2025
- CVE-2025-14443 — SSRF in
ose-openshift-apiserver(OpenShift API Server / ImageStreamImport image reference handling). Published 2025-12-16; CVSS v3.1 8.5 (High). The affected product shown is Red Hat OpenShift Container Platform 4 (packageopenshift4/ose-openshift-apiserver-rhel9). [1], [2]
Example OpenShift “API” product CVE in 2026 (affects “OpenShift API for Data Protection”, among others)
- CVE-2026-22772 — SSRF in Fulcio (MetaIssuer URL validation). Red Hat Security Data API listing shows Released on 2026-01-12, CVSS v3 5.8 (moderate), and advisories including RHSA-2026:2136 and RHSA-2026:2144; affected products listed include OpenShift API for Data Protection and Red Hat OpenShift Container Platform 4. [3]
OpenShift Container Platform errata that include 2025 CVEs (example)
- RHSA-2025:0654 (OCP 4.17.14) includes fixes for CVE-2025-21613 and CVE-2025-21614 (go-git issues), among others. [4]
How to find all relevant OpenShift CVEs for 2025–2026 (recommended)
Use Red Hat’s Security Data API “CVE” search endpoint and filter by product name (regex-supported), severity, and a date window (after/before). The available query parameters are documented by Red Hat. [5]
Tip: For OpenShift control-plane/API-server issues, search for product OpenShift Container Platform and then review CVEs where the affected package/component is openshift-apiserver / kube-apiserver / openshift4/ose-openshift-apiserver-*.
Sources:
[1] NVD entry for CVE-2025-14443.
[2] OpenCVE details showing Red Hat-provided package/product impact for CVE-2025-14443.
[3] Red Hat Security Data API CVE listing (shows CVE-2026-22772 advisories and affected products).
[4] Red Hat errata RHSA-2025:0654 (OCP 4.17.14) CVE list.
[5] Red Hat Security Data API documentation (CVE endpoints + parameters).
🏁 Script executed:
# Extract and analyze the pseudo-version information
echo "Analyzing pseudo-version information:"
echo "Old version: v0.0.0-20240830023148-b7d0481c9094"
echo "New version: v0.0.0-20260206223843-639b501bb529"
echo ""
echo "Pseudo-version format: v0.0.0-YYYYMMDDHHMMSS-COMMIT"
echo "Old: August 30, 2024"
echo "New: February 6, 2026"
echo "Time gap: ~18 months"Repository: openshift/cluster-api-provider-agent
Length of output: 330
Address breaking changes in openshift/api dependency update.
The update from v0.0.0-20240830023148-b7d0481c9094 to v0.0.0-20260206223843-639b501bb529 introduces breaking changes for Go consumers:
- Removed FeatureGate
VolumeAttributesClass(exported Go symbol removed) - Removed FeatureGate
ProcMountType(exported Go symbol removed) - Removed/graduated SDN-related feature gates
Verify that this codebase does not reference any of these removed feature gate constants or SDN-related gates. If it does, update the code accordingly or pin the dependency to a compatible version.
🤖 Prompt for AI Agents
In `@api/go.mod` at line 6, Search the codebase for references to the removed
OpenShift feature gate symbols (e.g., VolumeAttributesClass, ProcMountType) and
any SDN-related feature gate constants; if found (likely via imports from
github.com/openshift/api), update those call sites to either use the equivalent
string names or guarded logic (e.g., replace usages of the exported constants
FeatureGateVolumeAttributesClass/FeatureGateProcMountType with their literal
feature gate names or conditional runtime checks), or else pin the go.mod
dependency back to the older github.com/openshift/api version; make the change
in the functions/modules that import these symbols (replace constant references
or add compatibility wrappers) so the build no longer depends on the removed
exported symbols.
|
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
This PR contains the following updates:
b7d0481->26dbe2aConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.