doc:LRP skipRedirectFromBackend with per packet LB

[MitchLewis930]

User description

PR_042

---

PR Type

Documentation

---

Description

• Update LRP skipRedirectFromBackend documentation

• Clarify support for both socket-based and per-packet load-balancing

---

Diagram Walkthrough

flowchart LR
  A["skipRedirectFromBackend Feature"] -- "Previously: socket-based LB only" --> B["Updated Documentation"]
  A -- "Now: socket-based + per-packet LB" --> B

Loading

File Walkthrough

Relevant files

Documentation

local-redirect-policy.rst Clarify skipRedirectFromBackend LB support scope                  Documentation/network/kubernetes/local-redirect-policy.rst Updated documentation to clarify skipRedirectFromBackend support scope Changed from "only supported with socket-based load-balancing" to "supported with socket-based load-balancing and per packet based load-balancing" Maintains existing requirement for SO_NETNS_COOKIE feature in Linux kernel >= 5.8 +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.