Skip to content

Conversation

@zrggw
Copy link
Contributor

@zrggw zrggw commented Nov 24, 2025

Changes

  • Replaced workloadSelector with targetRefs in all EnvoyFilter examples throughout the rate limiting guide

Signed-off-by: aicee <hhbin2000@foxmail.com>
Copilot AI review requested due to automatic review settings November 24, 2025 04:37
@netlify
Copy link

netlify bot commented Nov 24, 2025

Deploy Preview for kmesh-net ready!

Name Link
🔨 Latest commit 7919477
🔍 Latest deploy log https://app.netlify.com/projects/kmesh-net/deploys/6923e3639dccab000891e2e1
😎 Deploy Preview https://deploy-preview-256--kmesh-net.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@kmesh-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hzxuzhonghu 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

@gemini-code-assist
Copy link

Summary of Changes

Hello @zrggw, 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 updates the documentation for rate limiting to align with recent API changes. It specifically modifies the EnvoyFilter examples to use targetRefs instead of the deprecated workloadSelector for specifying target resources, ensuring the guide provides accurate and up-to-date configuration patterns for users.

Highlights

  • Documentation Update: Replaced workloadSelector with targetRefs in all EnvoyFilter examples within the rate limiting guide to reflect current API usage.
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 successfully updates the documentation to replace workloadSelector with the more current targetRefs in the EnvoyFilter examples. The changes are accurate and reflect modern Istio configuration practices. However, I've identified an indentation error in one of the YAML examples that would cause it to fail if used directly. A code suggestion has been provided to correct this.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the rate limiting guide documentation to use the modern targetRefs field instead of the deprecated workloadSelector field in EnvoyFilter configurations. This change aligns with Kubernetes Gateway API patterns for targeting specific Gateway resources.

Key changes:

  • Updated prose description to reference targetRefs instead of workloadSelector
  • Replaced workloadSelector with targetRefs in all three EnvoyFilter examples
  • Updated selector format from label-based matching to Gateway resource reference

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@zrggw
Copy link
Contributor Author

zrggw commented Nov 24, 2025

I have replaced workloadSelector with targetRefs. @hzxuzhonghu @LiZhenCheng9527

Signed-off-by: aicee <hhbin2000@foxmail.com>
Copilot AI review requested due to automatic review settings November 24, 2025 04:47
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants