Skip to content

Draft: Fix Vendoring#496

Closed
dtfranz wants to merge 1 commit into
openshift:masterfrom
dtfranz:vendor-update
Closed

Draft: Fix Vendoring#496
dtfranz wants to merge 1 commit into
openshift:masterfrom
dtfranz:vendor-update

Conversation

@dtfranz

@dtfranz dtfranz commented Jun 1, 2023

Copy link
Copy Markdown
Contributor

The make verify ci has been failing, this is an attempt to fix it.

Signed-off-by: dtfranz <dfranz@redhat.com>
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 1, 2023
@openshift-ci

openshift-ci Bot commented Jun 1, 2023

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@dtfranz

dtfranz commented Jun 1, 2023

Copy link
Copy Markdown
Contributor Author

/test all

@openshift-ci

openshift-ci Bot commented Jun 1, 2023

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dtfranz
Once this PR has been reviewed and has the lgtm label, please assign kevinrizza for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci

openshift-ci Bot commented Jun 1, 2023

Copy link
Copy Markdown
Contributor

@dtfranz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-olm-flaky 83ac19f link false /test e2e-gcp-olm-flaky
ci/prow/unit-psm 83ac19f link true /test unit-psm
ci/prow/e2e-gcp-console-olm 83ac19f link true /test e2e-gcp-console-olm
ci/prow/unit-olm 83ac19f link true /test unit-olm
ci/prow/images 83ac19f link true /test images
ci/prow/e2e-gcp-olm 83ac19f link true /test e2e-gcp-olm
ci/prow/e2e-gcp-ovn 83ac19f link true /test e2e-gcp-ovn
ci/prow/e2e-upgrade 83ac19f link true /test e2e-upgrade
ci/prow/unit-registry 83ac19f link true /test unit-registry

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@dtfranz dtfranz closed this Jun 1, 2023
openshift-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Jun 6, 2026
…les (openshift#496)

* fix: stop emitting false-positive deprecated-API warnings for RBAC rules

RBAC PolicyRules only specify apiGroups and resources, not versions.
The deprecatedGroupResource map was flagging any RBAC rule that
referenced a group+resource combination where a beta version had been
removed, even when a stable version still exists in the same group.

This produced false-positive warnings for operators that use stable
APIs like batch/v1 CronJob, autoscaling/v2 HPA, events.k8s.io/v1
Event, policy/v1 PDB, discovery.k8s.io/v1 EndpointSlice, and
node.k8s.io/v1 RuntimeClass.

Remove these entries from the deprecatedGroupResource map since RBAC
rules for them are valid. Keep only PodSecurityPolicy, which was
entirely removed in v1.25 with no stable replacement in the policy
group.

The deprecatedGvk check (for actual versioned manifests in the bundle)
is unaffected and continues to correctly flag deprecated objects.

Fixes openshift#378

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>

* refactor: rename deprecatedGroupResource to removedGroupResource

Rename identifiers to match actual semantics: this map tracks
resources entirely removed from their API group, not merely
deprecated. Renames deprecatedGroupResource -> removedGroupResource
and warnIfDeprecated -> warnIfRemoved.

Suggested-by: Copilot
Requested-by: perdasilva
Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>

---------

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
Upstream-repository: api
Upstream-commit: 86d7cedb27dc0ec9a67903e4cf6ea18b31c80562
openshift-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Jun 9, 2026
…les (openshift#496)

* fix: stop emitting false-positive deprecated-API warnings for RBAC rules

RBAC PolicyRules only specify apiGroups and resources, not versions.
The deprecatedGroupResource map was flagging any RBAC rule that
referenced a group+resource combination where a beta version had been
removed, even when a stable version still exists in the same group.

This produced false-positive warnings for operators that use stable
APIs like batch/v1 CronJob, autoscaling/v2 HPA, events.k8s.io/v1
Event, policy/v1 PDB, discovery.k8s.io/v1 EndpointSlice, and
node.k8s.io/v1 RuntimeClass.

Remove these entries from the deprecatedGroupResource map since RBAC
rules for them are valid. Keep only PodSecurityPolicy, which was
entirely removed in v1.25 with no stable replacement in the policy
group.

The deprecatedGvk check (for actual versioned manifests in the bundle)
is unaffected and continues to correctly flag deprecated objects.

Fixes openshift#378

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>

* refactor: rename deprecatedGroupResource to removedGroupResource

Rename identifiers to match actual semantics: this map tracks
resources entirely removed from their API group, not merely
deprecated. Renames deprecatedGroupResource -> removedGroupResource
and warnIfDeprecated -> warnIfRemoved.

Suggested-by: Copilot
Requested-by: perdasilva
Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>

---------

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
Upstream-repository: api
Upstream-commit: 86d7cedb27dc0ec9a67903e4cf6ea18b31c80562
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant