SLEAK-6054: cost review tutorial#219
Draft
agustinoli wants to merge 2 commits into
Draft
Conversation
Add a tutorial covering how to read and interpret costs already being spent in SleakOps — the Cost Explorer dashboard, drilling down into Kubecost at the cluster level, and what to check when Cost Allocation Tags aren't active yet. Complements the existing optimize-aws-costs and nodepool-strategies tutorials, which cover reducing costs rather than reading them.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add a pointer to the new Cost Review Guide from optimize-aws-costs and nodepool-strategies (EN+ES), so readers land on how to read their current spend before applying an optimization strategy.
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
1 participant
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
/billing), drilling down into Kubecost at the cluster level, where costs come from (nodepool strategy, workload sizing, cluster uptime), and what to check if Cost Allocation Tags aren't active yet.optimize-aws-costsandnodepool-strategiestutorials, which cover reducing costs rather than reading them — cross-linked both ways.Test plan
npx docusaurus build --out-dir <tmp>— clean, no broken links/anchors on the new pagesTODOcomments — no browser available in the environment this was drafted in)SLEAK-6054