test: expand LRP test to include lifecycle events

[karina-ranadive]

Reason for Change:
Test Steps:

1. Initial Validation - Performs an initial DNS test to verify LRP is working correctly with metrics validation
2. Cilium Command Validation - Uses Cilium CLI commands to validate that LRP is properly configured in the Cilium dataplane, checking both cilium lrp list and cilium service list outputs
3. Pod Restart Testing - Restarts client pods and verifies that LRP functionality persists after pod restarts, ensuring the policy survives pod lifecycle changes
4. Post-Restart Validation - Re-runs DNS tests and Cilium validation to confirm LRP still works after client pod restarts
5. Resource Recreation Testing:

• Deleting client daemonsets and LRP resources
• Recreating the LRP policy
• Restarting node-local-dns pods to pick up the new configuration
• Recreating client daemonsets

6. Port Forward Re-establishment - Sets up a new port forward to the newly restarted node-local-dns pod (using a different local port to avoid conflicts)
7. Final Metrics Validation - Validates that DNS requests are properly redirected to the new node-local-dns pod through metrics monitoring
8. Final Cilium Validation - Performs a final check using Cilium commands to ensure LRP is still active after all the resource recreation

Purpose: This comprehensive lifecycle test ensures that Local Redirect Policy functionality is robust and survives various operational scenarios including pod restarts, resource deletion/recreation, and service restarts - validating both functional behavior through DNS metrics and dataplane configuration through Cilium CLI inspection.

Issue Fixed:

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• relevant PR labels added

Notes:

[Copilot]

Pull Request Overview

Adds negative Local Redirect Policy (LRP) test scenarios and parameterizes Prometheus endpoint usage in existing LRP tests.

• Extends testLRPCase to accept a Prometheus address for flexible metric validation.
• Introduces comprehensive negative and resilience LRP tests (resource recreation, pod restarts, cilium validation).
• Adds helper functions for validating Cilium LRP state and recreating test resources.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
test/integration/lrp/lrp_test.go	Adds negative LRP test flow, Prometheus address parameter, and Cilium/LRP validation helpers.
test/integration/lrp/lrp_fqdn_test.go	Updates calls to testLRPCase to include the new Prometheus address parameter.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (1)

test/integration/lrp/lrp_test.go:517

• The rand.Seed() call is made every time TakeOne() is invoked, which can cause issues in concurrent tests or when called multiple times in quick succession (as the seed would be very similar). Additionally, rand.Seed() has been deprecated since Go 1.20 in favor of using the global generator which is automatically seeded.

Recommendation: Remove the rand.Seed() call and use the global random generator directly, which is automatically seeded in Go 1.20+:

func TakeOne[T any](slice []T) T {
    if len(slice) == 0 {
        var zero T
        return zero
    }
    return slice[rand.Intn(len(slice))]
}

Alternatively, if you need better randomness, use crypto/rand or math/rand/v2 for Go 1.22+.

// TakeOne takes one item from the slice randomly; if empty, it returns the empty value for the type
// Use in testing only
func TakeOne[T any](slice []T) T {
	if len(slice) == 0 {
		var zero T
		return zero
	}
	rand.Seed(uint64(time.Now().UnixNano()))

---

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

[paulyufan2]

/azp run Azure Container Networking PR

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).