WIP: Fix flaky e2e-gcp-console secrets tests and SecretData React bug

[perdasilva]

Summary

The e2e-gcp-console CI job has had a 0% pass rate since Feb 2026 (186 builds analyzed). The dominant recent failure mode is flaky timeouts in the crud/secrets Cypress tests, blocking at least 10 PRs including several CVE fixes.

This PR addresses three root causes identified through build log analysis across the full job history:

• Fix React anti-pattern in SecretData component — setState was being called inside useMemo in configmap-and-secret-data.tsx, violating React's expectation that useMemo callbacks are pure. The hasRevealableContent state variable also had a stale closure bug (missing from the dependency array). Fixed by computing hasRevealableContent as a derived value alongside dataDescriptionList in a single useMemo, eliminating the separate useState entirely.

• Increase Cypress timeout and retries — defaultCommandTimeout increased from 30s to 40s, retries.runMode from 1 to 2. The CI environment provisions fresh GCP clusters per run, making API responses slower than the 30s timeout allows. Other tests in the suite already use 90s per-assertion timeouts for similar reasons.

• Add explicit data-load wait — detailsPageIsLoaded() helper now waits for [data-test="secret-data"] to exist, ensuring the K8s API response has arrived and SecretData has rendered before tests interact with the page. Also consolidated key-value.cy.ts to use this helper instead of duplicating the checks inline.

Test plan

• TypeScript compiles cleanly (no new errors in modified files)
• ESLint passes (pre-commit hook ran successfully)
• e2e-gcp-console CI job passes on this PR
• Verify "Reveal values" button still works on the Secrets detail page
• Verify secret CRUD operations work end-to-end

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 78ac48a9-fa63-4977-9aaf-29a53ef86820

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: perdasilva
Once this PR has been reviewed and has the lgtm label, please assign vojtechszocs for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[perdasilva]

/retest

[openshift-ci]

@perdasilva: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-console	d2d0e33	link	true	/test e2e-gcp-console

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.