[Misc] Use domain-qualified finalizer name

[Jeffwan]

Pull Request Description

Use domain-qualified finalizer name to avoid potential conflicts.

I0706 07:33:29.414963       1 warning_handler.go:65] "msg"="metadata.finalizers: \"stormservice-finalizer\": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers" "logger"="KubeAPIWarningLogger"

Related Issues

Resolves: #1254

Important: Before submitting, please complete the description above and review the checklist below.

---

Contribution Guidelines (Expand for Details)

We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:

Pull Request Title Format

Your PR title should start with one of these prefixes to indicate the nature of the change:

• [Bug]: Corrections to existing functionality
• [CI]: Changes to build process or CI pipeline
• [Docs]: Updates or additions to documentation
• [API]: Modifications to aibrix's API or interface
• [CLI]: Changes or additions to the Command Line Interface
• [Misc]: For changes not covered above (use sparingly)

Note: For changes spanning multiple categories, use multiple prefixes in order of importance.

Submission Checklist

• PR title includes appropriate prefix(es)
• Changes are clearly explained in the PR description
• New and existing tests pass successfully
• Code adheres to project style and best practices
• Documentation updated to reflect changes (if applicable)
• Thorough testing completed, no regressions introduced

By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.

[gemini-code-assist]

Summary of Changes

Hello @Jeffwan, I'm Gemini Code Assist¹! 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 addresses potential naming conflicts for finalizers by adopting a domain-qualified naming convention. By prefixing finalizer names with orchestration.aibrix.ai, it ensures uniqueness and prevents clashes with other components or third-party integrations, enhancing the robustness and stability of the system's resource management.

Highlights

• Finalizer Naming Convention: Updated the RoleSetFinalizer constant in pkg/controller/roleset/roleset_controller.go from "roleset-finalizer" to "roleset.orchestration.aibrix.ai/finalizer".
• Finalizer Naming Convention: Updated the StormServiceFinalizer constant in pkg/controller/stormservice/stormservice_controller.go from "stormservice-finalizer" to "stormservice.orchestration.aibrix.ai/finalizer".

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the finalizer names for RoleSet and StormService to be domain-qualified, preventing potential conflicts. The suggested finalizer names, following the domain/resource format, align with Kubernetes conventions, enhancing consistency and clarity.

[kr11]

lgtm.