Remove unused permission for knative in RBAC

[jenniferubah]

Description

Remove unused RBAC permissions for Knative resources

Which issue(s) does this PR fix or relate to

• relates to PR: Add knative crds + move knative CRs to plugin-infra #1219

PR acceptance criteria

• Tests
• Documentation

Summary by Sourcery

Enhancements:

• Remove unused ClusterRole rules for operator.knative.dev resources (knativeeventings and knativeservings) and their verbs.

[sourcery-ai]

Reviewer's Guide

This PR streamlines the RBAC configuration by removing an unused Knative apiGroup section from the SonataFlow plugin’s ClusterRole, deleting permissions for knativeeventings and knativeservings resources.

Entity relationship diagram for updated RBAC rules in SonataFlow plugin

erDiagram
    ClusterRole ||--o{ Rule : contains
    Rule {
        string apiGroups
        string resources
        string verbs
    }

    %% Previously, there was a Rule for operator.knative.dev (knativeeventings, knativeservings)
    %% This rule has now been removed, so it is not present in the updated diagram.

    ClusterRole {
        string name
    }

Loading

File-Level Changes

Change	Details	Files
Removed unused Knative resources permissions	Deleted operator.knative.dev apiGroup block Removed knativeeventings and knativeservings resources Removed all associated verbs (create, delete, get, list, patch, update, watch)	config/profile/rhdh/plugin-rbac/rbac-sonataflow.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @jenniferubah - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

⚠️ Files changed in bundle and installer generation!

Those changes to the operator bundle/installer manifests should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

[rm3l]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gazarenkov, rm3l

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [gazarenkov,rm3l]

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

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.7.0-pr-1320-fe5e838
2. https://quay.io/rhdh-community/operator-bundle:0.7.0-pr-1320-fe5e838
3. https://quay.io/rhdh-community/operator-catalog:0.7.0-pr-1320-fe5e838