docs(cost): add GCP billing setup guide for mc-cost-optimizer 0.6.5 - #206
Merged
Merged
Conversation
- docs/cost-optimizer-gcp-billing.md: BigQuery billing export prerequisites, OpenBao csp/gcp admin SA and required roles, /api/gcp/setup flow (auto-provision -> dataset -> billing-confirmed), collector restart, verification and troubleshooting, legacy (<=0.6.0) env method - .env.setup: add Cost-GCP-Collector section comments; drop MC_COST_OPTIMIZER_GCP_BQ_DATASET/TABLE (ignored since 0.6.5) - docker-compose.yaml: drop gcp.dataset/gcp.table env from gcp-collector - README.md: link the guide; add Azure/NCP/GCP collector ports
docs(cost): add GCP billing setup guide for mc-cost-optimizer 0.6.5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents how to enable GCP billing collection in mc-cost-optimizer.
This PR also removes GCP env settings that the 0.6.5 images no longer read.
Changes
gcp_billing_export_v1_<BILLING_ACCOUNT_ID>)secret/csp/gcpand the roles it needs/api/gcp/setupflow: status → auto-provision → dataset → billing-confirmed → collector restart/admin/billing/collect, SQL), troubleshooting, and the legacy (≤0.6.0) env method## Cost-GCP-Collectorsection with commentsMC_COST_OPTIMIZER_GCP_BQ_DATASET/MC_COST_OPTIMIZER_GCP_BQ_TABLE, which 0.6.5 ignores (dataset/table now come from OpenBaosecret/cost/gcpor auto-discovery)gcp.dataset/gcp.tableenv lines frommc-cost-optimizer-gcp-collectorVerification
Tested on a local stack with
mc-costopti-api/mc-costopti-gcpcollector0.6.5.csp/gcpand auto-discovered the billing table. With Standard and Detailed exports in the same dataset, it picked the Detailed table. Manual collection: COMPLETED.auto-provisionfailed atSA key generationwith 403iam.serviceAccountKeys.create.roles/iam.serviceAccountKeyAdmin, all steps returned OK.dataset (existing)→billing-confirmed→ stageCOMPLETE.cost/gcp (운영 SA), and manual collection completed.bao kv patch secret/cost/gcp table=...followed by a collector restart. BE/statusshowed the new table only after a BE restart.docker compose config -qpasses with.env.setup, and the README links resolve.