Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENHANCEMENT] Enable Dynamic Cluster Configuration Updates for QA Automated Tests #2770

Open
Tracked by #2774
slolatte opened this issue Jan 15, 2025 · 0 comments
Open
Tracked by #2774
Labels
kind/enhancement New feature or request

Comments

@slolatte
Copy link

Describe the use case:

In QA, we often need to test specific features by enabling or disabling them dynamically during the execution of automated Playwright test runs. Examples of such features include:

  • Resource-Based Authorization (RBA)
  • Multi-Tenancy
  • User Access Restrictions
  • Updating License Keys

Currently, the only way to achieve this is by regenerating the Helm chart, which is inefficient and time-consuming. A more streamlined approach is required to support these configurations.

Describe the enhancement/feature:

We propose adding the ability to update the CI cluster dynamically via a script or API that can be triggered directly from the Playwright test suite. This script should:

  1. Allow feature toggles or updates (e.g., enable/disable RBA, change tenancy settings, update license keys).
  2. Apply the changes without requiring a full cluster recreation.

This would enable more efficient and flexible testing of various features and configurations in automated scenarios.

Desired outcome and acceptance tests:

Desired Outcome:

  • QA engineers can dynamically update the cluster's configuration during test runs without regenerating the Helm chart.

This feature will empower the QA team to test more complex scenarios effectively and save time during test execution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant