You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resources created by the test are not immediately cleaned up, leaving debris in the cluster
Logs from the test pod are not added to the plugin resource status field. This forces users to manually run helm test in remote clusters to debug test failures, leading to delays in troubleshooting.
Acceptance Criteria
Test Pod Logs in Plugin CR Status Field:
Logs from the Helm test pod are captured upon test completion and appended to the status field of the plugin custom resource (CR).
Logs are concise, well-formatted, and user-friendly for quick debugging.
Users can view the test logs directly in the plugin CR status without manually interacting with the cluster.
Resource Cleanup:
All resources created during a Helm test are cleaned up immediately, regardless of whether the test passes or fails.
The test cluster is left in a clean state after every test run, with no orphaned resources or debris.
Cleanup logic addresses ConfigMaps, Pods, RBAC permissions, and any other resources created during tests.
Priority
None
Is your feature request related to a problem?
Currently, when a Helm chart test fails:
helm test
in remote clusters to debug test failures, leading to delays in troubleshooting.Acceptance Criteria
Test Pod Logs in Plugin CR Status Field:
status
field of the plugin custom resource (CR).Resource Cleanup:
Update Documentation
Additional context.
No response
Reference Issues
Depends on cloudoperators/greenhouse#585
The text was updated successfully, but these errors were encountered: