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

Migrate Cypress dashboard to AWS #13148

Closed
cnotv opened this issue Jan 17, 2025 · 5 comments
Closed

Migrate Cypress dashboard to AWS #13148

cnotv opened this issue Jan 17, 2025 · 5 comments
Assignees
Labels
area/ci CI and automation related, e.g. GitHub Actions area/e2e area/test Test (e2e and unit) kind/tech-debt Technical debt QA/None
Milestone

Comments

@cnotv
Copy link
Member

cnotv commented Jan 17, 2025

Description

Cloud services are shifting to AWS. Create instance for Sorry Cypress and update IP defined for the E2E tests.

Content

Install latest version of SorryCypress.
Define reverse proxy rules to redirect to port 80, and disallow all the other ports.
Possibly host video in separated storage to avoid memory issues.

@cnotv cnotv added area/ci CI and automation related, e.g. GitHub Actions area/e2e area/test Test (e2e and unit) kind/tech-debt Technical debt labels Jan 17, 2025
@cnotv cnotv added this to the v2.11.0 milestone Jan 17, 2025
@cnotv cnotv self-assigned this Jan 17, 2025
@cnotv
Copy link
Member Author

cnotv commented Jan 21, 2025

During the migration, we should also consider the cleanup process mentioned here: #8955

@cnotv
Copy link
Member Author

cnotv commented Jan 21, 2025

Another issue to consider is the different adopted library as mentioned in #10137

@cnotv
Copy link
Member Author

cnotv commented Jan 21, 2025

We should consider the possibility of adding an SSL certificate as defined in: #6789

@cnotv
Copy link
Member Author

cnotv commented Jan 23, 2025

As a recap for the dashboard code state, the library has been practically discontinued after the Cypress official post last year, while the author moved his paid service to Playwright.

I would consider then the need to find an alternative to the current state of art. As solution to this issue, the same code will be adopted for AWS.

@rancher-max please discuss with the QA team about this. I leave to you guys find an alternative till things are still up and running.
FYI the last supported Cypress should be 13 but that would require several updates which do not seem to make sense in this scenario.

@cnotv
Copy link
Member Author

cnotv commented Jan 23, 2025

Closing issue given the circumstances and to be replaced by other tools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci CI and automation related, e.g. GitHub Actions area/e2e area/test Test (e2e and unit) kind/tech-debt Technical debt QA/None
Projects
None yet
Development

No branches or pull requests

1 participant