Skip to content

[Long Running Tests] Remove Hardcoded List of Test Namespaces in Cleanup Step #7966

Closed as not planned

Description

@kachawla

Area for Improvement

Long running test workflow - cleanup cluster step.

Observed behavior

Each execution of the long running tests includes a cleanup step that removes multiple namespaces created by the functional tests. Currently the process for identifying which namespaces to delete relies on a hardcoded list, which is expected to be updated manually whenever a new namespace is added as a part of a functional test. This approach is fragile because it depends on legacy knowledge and puts the onus on contributors to read documentation (which I don't believe exists today for this). An example of this issue can be found here.

Desired behavior

Remove the hardcoded list of namespaces that is duplicated across the functional tests and the long running test workflow.

Proposed Fix

We should remove the dependency on a hardcoded list by either establishing a single source of truth for test namespaces, or a less involved solution would be to delete everything except radius-system + any other namespace we want retain across runs.

rad Version

Not applicable. Applies to all versions.

Operating system

No response

Additional context

No response

Would you like to support us?

  • Yes, I would like to support you

AB#13249

Activity

  1. added
    maintenanceIssue is a non-user-facing task like updating tests, improving automation, etc..
    on Sep 25, 2024
  2. radius-triage commented on Sep 25, 2024

    @radius-triage

    👋 @kachawla Thanks for filing this issue.

    A project maintainer will review this issue and get back to you soon.

    We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

    For more information on our triage process please visit our triage overview

  3. radius-triage commented on Sep 26, 2024

    @radius-triage

    👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

    We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

    For more information on our triage process please visit our triage overview

  4. sylvainsf commented on Nov 13, 2024

    @sylvainsf
    Contributor

    Impact is breaking long running test cluster if we forget to add a namespace.

  5. nicolejms commented on Jun 19, 2026

    @nicolejms
    Contributor

    stale issue so closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintenanceIssue is a non-user-facing task like updating tests, improving automation, etc..triagedThis issue has been reviewed and triaged

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions