[ci] Upload autoscaling in K8s test results

[selenium-ci]

This PR contains the results of the autoscaling tests in Kubernetes

[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
Update

Compliance status legend

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

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Avoid committing test results into Git Avoid storing raw test results in Git to prevent repository bloat. Instead, use an artifact repository and have the CI pipeline publish results to a dashboard for analysis. Examples: .keda/results_test_k8s_autoscaling_deployment_count.md [1-22] | Iteration | New request sessions | Sessions created time | Sessions failed to create | New pods scaled up | Total running sessions | Total running pods | Max sessions per pod | Gaps | Sessions closed | | --------- | -------------------- | --------------------- | ------------------------- | ------------------ | ---------------------- | ------------------ | -------------------- | ---- | --------------- | | 1 | 2 | 0.09 s | 2 | 0 | 0 | 0 | 1 | 0 | 0 | | 2 | 3 | 48.48 s | 0 | 3 | 3 | 3 | 1 | 0 | 0 | | 3 | 3 | 74.70 s | 0 | 5 | 6 | 8 | 1 | 2 | 0 | | 4 | 1 | 22.30 s | 0 | 1 | 7 | 9 | 1 | 2 | 0 | | 5 | 2 | 39.01 s | 0 | 2 | 9 | 11 | 1 | 2 | 0 | | 6 | 2 | 46.18 s | 0 | 2 | 11 | 13 | 1 | 2 | 11 | | 7 | 2 | 21.02 s | 0 | 0 | 2 | 13 | 1 | 11 | 0 | | 8 | 3 | 16.96 s | 0 | 0 | 5 | 13 | 1 | 8 | 0 | ... (clipped 12 lines) .keda/results_test_k8s_autoscaling_deployment_count_in_chaos.md [1-22] | Iteration | New request sessions | Sessions created time | Sessions failed to create | New pods scaled up | Total running sessions | Total running pods | Max sessions per pod | Gaps | Sessions closed | | --------- | -------------------- | --------------------- | ------------------------- | ------------------ | ---------------------- | ------------------ | -------------------- | ---- | --------------- | | 1 | 4 | 65.28 s | 0 | 6 | 4 | 6 | 1 | 2 | 4 | | 2 | 5 | 45.63 s | 0 | 2 | 5 | 8 | 1 | 3 | 5 | | 3 | 3 | 5.61 s | 0 | 0 | 3 | 8 | 1 | 5 | 3 | | 4 | 6 | 45.56 s | 0 | 1 | 6 | 9 | 1 | 3 | 6 | | 5 | 5 | 15.76 s | 0 | 1 | 5 | 10 | 1 | 5 | 5 | | 6 | 5 | 16.98 s | 0 | 1 | 5 | 11 | 1 | 6 | 3 | | 7 | 6 | 53.81 s | 0 | 2 | 8 | 13 | 1 | 5 | 8 | | 8 | 4 | 16.04 s | 0 | 0 | 4 | 13 | 1 | 9 | 4 | ... (clipped 12 lines) Solution Walkthrough: Before: // Process: Test results are stored as markdown files in the git repository. // A PR is created to update these files after each test run. // .keda/results_test_k8s_autoscaling_deployment_count.md | Iteration | New request sessions | Sessions created time | ... | | --------- | -------------------- | --------------------- | --- | | 1 | 2 | 0.09 s | ... | | 2 | 3 | 48.48 s | ... | | ... | ... | ... | ... | After: // Process: Test results are handled by a CI/CD pipeline. // 1. Tests are executed. // 2. Results are uploaded to an artifact storage (e.g., S3, Artifactory). // 3. A dashboard or reporting tool consumes the results for visualization. // The git repository no longer stores the raw result files. // Repository state: // .keda/ folder does not contain result*.md files. // Git history is clean from test result data churn. Suggestion importance[1-10]: 8 __ Why: The suggestion addresses the entire PR's purpose by highlighting a significant repository management anti-pattern and proposing a standard, more scalable solution.	Medium
General	Automate markdown report Automate the generation of markdown report tables from test results to prevent manual errors and ensure data consistency across files. .keda/results_test_k8s_autoscaling_deployment_count_with_node_max_sessions.md [1] -| Iteration | New request sessions | Sessions created time | Sessions failed to create | New pods scaled up | Total running sessions | Total running pods | Max sessions per pod | Gaps | Sessions closed | +```bash +./scripts/generate_k8s_autoscaling_report.sh --mode=deployment --output .keda/results_test_k8s_autoscaling_*.md +``` Apply / Chat Suggestion importance[1-10]: 2 __ Why: This is a general process improvement suggestion that is not directly related to the code changes in the PR, which only involve updating data in existing markdown files.	Low
Update