Automate workspace startup verification against the proxy Openshift cluster #21446
Closed
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
area/qe
kind/task
Internal things, technical debt, and to-do tasks to be performed.
severity/P1
Has a major impact to usage or development of the system.
Is your task related to a problem? Please describe
proxy and airgap-related issues are discovered very late during the pre-release testing. Need to automate the basic workspace startup flow against the proxy OpenShift 4.10 cluster
Describe the solution you'd like
A periodic nightly job that:
Describe alternatives you've considered
probably we should start the automation with the
che-code
based workspacesAdditional context
No response
The text was updated successfully, but these errors were encountered: