Skip to content

docs: add comprehensive GCP GKE self-hosting guide#5303

Merged
vmatsiiako merged 3 commits intomainfrom
devin/1769626427-improve-gcp-native-guide
Feb 4, 2026
Merged

docs: add comprehensive GCP GKE self-hosting guide#5303
vmatsiiako merged 3 commits intomainfrom
devin/1769626427-improve-gcp-native-guide

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Jan 28, 2026

Context

This PR adds a new comprehensive self-hosting guide for deploying Infisical on Google Cloud Platform using GKE, Cloud SQL (PostgreSQL), and Memorystore (Redis). This addresses the missing GCP deployment documentation identified in PR #5106.

The guide includes:

  • System requirements table
  • Step-by-step deployment with verification commands after each major step
  • SMTP/email configuration section
  • Debugging with kubectl exec
  • Database migration handling
  • Clean up/delete resources instructions
  • Infrastructure as Code (Terraform example)
  • Comprehensive troubleshooting section (7 common issues)

Fixes from original PR #5106:

  • Fixed "CloudWatch Alarms" terminology (AWS term) - removed in favor of GCP-native "Cloud Monitoring alerts"
  • Fixed Helm repo name to use infisical-helm-charts for consistency with other guides

Updates since last revision

  • Addressed Greptile feedback: Replaced all PROJECT_ID placeholders with <YOUR_PROJECT_ID> to make it more obvious that users need to substitute their actual GCP project ID

Steps to verify the change

  1. Preview the documentation in Mintlify to verify formatting renders correctly
  2. Spot-check gcloud CLI commands for syntax correctness
  3. Verify Terraform HCL example is syntactically valid
  4. Confirm the guide follows the same structure as the AWS guide

Human review checklist

  • Verify gcloud CLI commands are syntactically correct
  • Verify Terraform configuration is valid HCL
  • Confirm Helm repo name infisical-helm-charts matches other guides
  • Verify health check endpoint /api/status is correct for Infisical
  • Check Mintlify preview renders properly
  • Verify all placeholder values (<YOUR_PROJECT_ID>, <your-secure-password>, etc.) are clearly marked for user replacement

Type

  • Fix
  • Feature
  • Improvement
  • Breaking
  • Docs
  • Chore

Checklist

  • Title follows the conventional commit format: type(scope): short description (scope is optional, e.g., fix: prevent crash on sync or fix(api): handle null response).
  • Tested locally
  • Updated docs (if needed)
  • Read the contributing guide

Link to Devin run: https://app.devin.ai/sessions/de8b36ae4d4c4287ace71741aef029fe
Requested by: ashwin@infisical.com

- Add complete deployment guide for GCP using GKE, Cloud SQL, and Memorystore
- Fix CloudWatch Alarms bug (changed to Cloud Monitoring alerts)
- Fix helm repo name to use infisical-helm-charts for consistency
- Add system requirements table
- Add verification steps after each major step
- Add SMTP/email configuration section
- Add debugging with kubectl exec section
- Add database migration handling
- Add clean up/delete resources section
- Add Infrastructure as Code (Terraform) example
- Add comprehensive troubleshooting section (7 common issues)
- Add auto-scaling configuration section

Co-Authored-By: ashwin@infisical.com <ashwin@infisical.com>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@maidul98
Copy link
Collaborator

maidul98 commented Jan 28, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Jan 28, 2026

Greptile Overview

Greptile Summary

Added comprehensive GCP GKE self-hosting guide with step-by-step deployment instructions for Cloud SQL (PostgreSQL), Memorystore (Redis), and Google-managed certificates.

The guide includes:

  • Clear system requirements table with minimum and production recommendations
  • Detailed networking setup (VPC, subnets, firewall rules, Cloud NAT)
  • Security best practices (private nodes, workload identity, encryption key management)
  • SMTP configuration, debugging commands, and database migration handling
  • Terraform IaC example for infrastructure automation
  • Extensive troubleshooting section covering 7 common deployment issues

All <YOUR_PROJECT_ID> placeholders are clearly marked for user substitution as requested in previous feedback. The Helm repo name uses infisical-helm-charts for consistency with other deployment guides.

Confidence Score: 5/5

  • This documentation-only PR is safe to merge with no risk to production systems
  • This is a documentation-only change that adds a new self-hosting guide. No code changes, no breaking changes, and the previous feedback about placeholder formatting has been addressed. The guide follows documentation best practices with clear structure, verification steps, and comprehensive troubleshooting.
  • No files require special attention

Important Files Changed

Filename Overview
docs/docs.json Added new GCP deployment guide to navigation menu
docs/self-hosting/deployment-options/gcp-native.mdx Comprehensive GCP GKE deployment guide with Cloud SQL, Memorystore, security best practices, and troubleshooting

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 files reviewed, 5 comments

Edit Code Review Agent Settings | Greptile

Address Greptile feedback to make placeholder values more obvious
for users to identify and replace with their actual GCP project ID.

Co-Authored-By: ashwin@infisical.com <ashwin@infisical.com>
@ashwin-infisical
Copy link
Collaborator

@greptileai Can you re-review this PR with all of your comments addressed?

The docs.json navigation updates will be handled in a separate PR (#5305).

Co-Authored-By: ashwin@infisical.com <ashwin@infisical.com>
@vmatsiiako vmatsiiako merged commit 09b5adc into main Feb 4, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants