Skip to content

chore(role-instance): add roleinstance related rbac#199

Merged
cheyang merged 1 commit intosgl-project:mainfrom
Syspretor:feature/add-roleinstance-rbac
Mar 13, 2026
Merged

chore(role-instance): add roleinstance related rbac#199
cheyang merged 1 commit intosgl-project:mainfrom
Syspretor:feature/add-roleinstance-rbac

Conversation

@Syspretor
Copy link
Collaborator

Ⅰ. Motivation

Ⅱ. Modifications

Ⅲ. Does this pull request fix one issue?

fixes #XXXX

Ⅳ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.

Ⅴ. Describe how to verify it

VI. Special notes for reviews

Checklist

  • Format your code make fmt.
  • Add unit tests or integration tests.
  • Update the documentation related to the change.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces essential Role-Based Access Control (RBAC) permissions. It expands the existing ClusterRole definition to include new roleinstancesets and roleinstances resources, thereby enabling necessary interactions with these components within the Kubernetes environment.

Highlights

  • RBAC Permissions: Added roleinstancesets and roleinstances to the resources list within the clusterrole.yaml to ensure proper Role-Based Access Control for these new resource types.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • deploy/helm/rbgs/templates/clusterrole.yaml
    • Added roleinstancesets to the list of accessible resources.
    • Added roleinstances to the list of accessible resources.
Activity
  • No specific activity (comments, reviews, progress updates) was found in the provided context.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds the necessary RBAC permissions for RoleInstance and RoleInstanceSet custom resources to the controller's ClusterRole. The change is correct and aligns with the introduction of these new resources. I've added one suggestion to improve maintainability by sorting the resource list alphabetically.

Comment on lines 40 to 45
- rolebasedgroupscalingadapters
- rolebasedgroups
- roleinstancesets
- roleinstances
- instancesets
- instances

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better maintainability and to avoid potential merge conflicts in the future, it's a good practice to keep lists like this sorted alphabetically.

      - instances
      - instancesets
      - rolebasedgroups
      - rolebasedgroupscalingadapters
      - roleinstances
      - roleinstancesets

@Syspretor Syspretor force-pushed the feature/add-roleinstance-rbac branch from 23aee44 to b75868e Compare March 13, 2026 11:24
Copy link
Collaborator

@cheyang cheyang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@cheyang cheyang merged commit 18c4037 into sgl-project:main Mar 13, 2026
5 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants