-
Notifications
You must be signed in to change notification settings - Fork 2
Update HTTPRoute and RuleSet with missing fields #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Adds fields to the HTTPRoute and RuleSet resources needed by ArgoCD to ensure the sync status is healthy. - Bumps the chart version to 0.4.7 Issue: LFXV2-511 Signed-off-by: Trevor Bramwell <[email protected]>
WalkthroughChart version bumped to 0.4.7. HTTPRoute template updated to use explicit Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant C as Client
participant GW as Gateway
participant HR as HTTPRoute
participant RS as Ruleset
participant S as Service
C->>GW: HTTP request
GW->>HR: Match via parentRefs (group/kind/name)
HR->>RS: Evaluate rules (incl. allow_encoded_slashes="off")
alt Encoded slashes disallowed
RS-->>HR: Deny/match-fail
HR-->>GW: No route / reject
GW-->>C: Error response
else Allowed
HR->>S: Forward to backendRefs (group="", kind=Service, name, weight:1)
S-->>HR: Service response
HR-->>GW: Return response
GW-->>C: Respond
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Pre-merge checks and finishing touches✅ Passed checks (5 passed)
✨ Finishing touches🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
Comment |
There was a problem hiding this 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 Helm chart for the lfx-v2-query-service to improve Gateway API compliance and security. The changes explicitly specify API groups and kinds for Gateway and Service references, add security configurations to prevent encoded slashes, and update the chart version.
- Added explicit
groupandkindfields to Gateway and Service references in HTTPRoute configuration - Enhanced security by adding
allow_encoded_slashes: "off"to all ruleset rules - Incremented chart version from 0.4.6 to 0.4.7
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| charts/lfx-v2-query-service/templates/httproute.yaml | Updated Gateway and Service references with explicit group and kind fields |
| charts/lfx-v2-query-service/templates/ruleset.yaml | Added allow_encoded_slashes security configuration to all rules |
| charts/lfx-v2-query-service/Chart.yaml | Bumped chart version to 0.4.7 |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
This is the default setting for the field and gets added when the resource is created in Kubernetes. Adding it explicitly to ensure ArgoCD's sync status is healthy. Signed-off-by: Trevor Bramwell <[email protected]>
This pull request updates the Helm chart for the
lfx-v2-query-service, primarily to enhance Gateway API compatibility and improve security settings in HTTP routing and ruleset configurations. The changes focus on explicitly specifying API groups and kinds in Gateway and Service references, and on adding a configuration to disallow encoded slashes in several rules.Gateway and Service Reference Updates:
groupandkindfields for Gateway references inhttproute.yamlto comply with Gateway API requirements.groupandkindfields for Service references in backend definitions inhttproute.yaml. [1] [2]Security and Ruleset Enhancements:
allow_encoded_slashes: "off"to all rules inruleset.yamlto prevent encoded slashes in URLs, improving security. [1] [2] [3] [4] [5]Chart Version Update:
0.4.6to0.4.7inChart.yaml.Issue: LFXV2-511