DOC-2277: Warn that BYOC GCP credential rotation needs Support#625
DOC-2277: Warn that BYOC GCP credential rotation needs Support#625micheleRP wants to merge 1 commit into
Conversation
Add a "Service account credential rotation" callout to the GCP IAM Policies and Create a BYOC Cluster on GCP pages, explaining that GCP service account credential rotation is not self-service and must be coordinated with Redpanda Support. The callout lives in a shared partial included by both pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughA new AsciiDoc partial file, Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
What
Adds a Service account credential rotation callout to two BYOC GCP pages:
cloud-iam-policies-gcp.adoc) — new section at the bottom.create-byoc-cluster-gcp.adoc) — section before "Next steps".The callout text lives in a single shared partial (
security:partial$byoc-gcp-credential-rotation.adoc) included by both pages, so it stays in sync.Why
Customer incident ZD-6896: a BYOC GCP customer rotated their GCP service account credentials without coordinating with Redpanda Support. The agent lost connectivity, the cluster stuck in "Upgrading," tiered storage was disrupted, and recovery took 8 days of Engineering effort. The docs never warned that credential rotation is not self-service. This PR closes that gap.
Resolves DOC-2277.
Notes
[WARNING]admonition for the not-self-service / disruption risk, with the "contact Support" instructions as body text above it.Preview pages
🤖 Generated with Claude Code