Skip to content

Commit

Permalink
Clean up content
Browse files Browse the repository at this point in the history
  • Loading branch information
davidcollom committed May 31, 2024
1 parent 1369200 commit 7875233
Show file tree
Hide file tree
Showing 4 changed files with 19 additions and 17 deletions.
6 changes: 3 additions & 3 deletions content/selection/automation-and-tooling.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Policies should cover:

#### [Kyverno](https://kyverno.io/)

Nirmata provide a collection of out-of-the-box FinOps and Cost-Optimisation policies (https://github.com/nirmata/finops-policies, https://nirmata.com/2023/03/22/kubernetes-finops-policies-with-kyverno/). May require some additional policiers - but this is a good starting point.
[Nirmata](https://nirmata.com/) provide a collection of 'out-of-the-box' FinOps and Cost-Optimisation policies (https://github.com/nirmata/finops-policies, https://nirmata.com/2023/03/22/kubernetes-finops-policies-with-kyverno/). May require some additional policiers - but this is a good starting point.
**Community recognition**: Not on FinOps landscape. CNCF Incubating Project.
**License**: Apache
**Level of Maintenance**: Actively maintained
Expand All @@ -46,7 +46,7 @@ Ideally tooling would:
Identify potential for discounts (e.g. Spot Instances or Commitments vs on-demand pricing)
Automate use of a cheaper machine type or machine discount model (i.e. Spot) where available

Capability: [Rate Optimisation](https://www.finops.org/framework/capabilities/rate-optimization/)
**Capability**: [Rate Optimisation](https://www.finops.org/framework/capabilities/rate-optimization/)

### Tooling considered

Expand All @@ -57,7 +57,7 @@ For any custom work, we should think about preferred direction:
- Provide automation for rate optimisation as 'opt-in'. In reality, this would be spot instances only.

## Workload optimisation
Capability: [Workload Optimisation](https://www.finops.org/framework/capabilities/workload-optimization/)
**Capability**: [Workload Optimisation](https://www.finops.org/framework/capabilities/workload-optimization/)

Consider:
- Horizontal scaling
Expand Down
6 changes: 3 additions & 3 deletions content/selection/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,13 @@ This project is aimed at engineering teams that are aiming to automate FinOps be

We believe that the key areas that the Engineering persona is trying to solve are:

- Monitoring
- **Monitoring**
- Gathering metrics/cost data
- Visualizing this data to teams and stakeholders
- Multi-Cloud cost data
- Alerting
- **Alerting**
- Anomaly management
- Automation of best practices such as:
- **Automation of best practices** such as:
- Right-sizing/workload optimization
- Providing sensible defaults
- Forecasting (how much will x cost(if…))?
Expand Down
18 changes: 10 additions & 8 deletions content/selection/monitoring.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
# Monitoring Selection

## Capability: [Allocation](https://www.finops.org/framework/capabilities/allocation/), [Reporting and Analytics](https://www.finops.org/framework/capabilities/reporting-analytics/)
**Capability**: [Allocation](https://www.finops.org/framework/capabilities/allocation/), [Reporting and Analytics](https://www.finops.org/framework/capabilities/reporting-analytics/)

## **Aims to understand**: What are we spending where?

Should cover:

- Spend
- Cost-allocation
- Gathering and visualising this data
Expand All @@ -13,16 +14,16 @@ Should cover:

### [OpenCost](https://www.opencost.io/)

A vendor-neutral open source project for measuring and allocating cloud infrastructure and container costs in real time.
Community recognition: A CNCF Sandbox Project, and part of FinOps Foundations Landscape, this project has strong credibility in this space.
"A vendor-neutral open source project for measuring and allocating cloud infrastructure and container costs in real time".
Community recognition: A CNCF Sandbox Project, and part of FinOps Foundation's Landscape, this project has strong credibility in this space.
Requires Prometheus to be installed.

**License**: Apache
**Level of Maintenance**: actively maintained.

**Provides**: metrics and visibility.
Does not provide: recommendations/reports (these are in Kubecost free).
Requires user configuration to get started (cant install and get running without a GCP api key if using google cloud - autodetected).
Requires user configuration to get started (can't install and get running without a GCP api key if using google cloud - autodetected).
**Installation**: first Prometheus, then Cloud provider configuration, then opencost.

### [KubeCost](https://www.kubecost.com/) (free tier)
Expand All @@ -37,15 +38,16 @@ Get data/running ui on install without any preconfiguration.

### [Crane](https://gocrane.io/)

A FinOps Platform for Cloud Resource Analytics and Economics in Kubernetes clusters.
Community recognition: On CNCF Landscape, not a CNCF Project, not on FinOps Foundations Landscape.
"A FinOps Platform for Cloud Resource Analytics and Economics in Kubernetes clusters."
Community recognition: On CNCF Landscape, not a CNCF Project, not on FinOps Foundation's Landscape.
**License**: Apache
**Level of Maintenance**: last release Jul 2023. Does not appear actively maintained.

### [Komiser](https://www.komiser.io/)

“A cloud-agnostic resource mananger… integrates with multiple cloud providers … builds a cloud asset inventory, and helps you break down your cost at the resource level 💰”
Community recognition: Not on CNCF Landscape, not a CNCF Project, not on FinOps Foundation’s Landscape. Has community following: 4.8k stars on GitHub.
"A cloud-agnostic resource mananger... integrates with multiple cloud providers … builds a cloud asset inventory, and helps you break down your cost at the resource level 💰"
Community recognition: Not on CNCF Landscape, not a CNCF Project, not on FinOps Foundation's Landscape.
Has community following: 4.8k stars on GitHub.
**License**: Elastic License (ELv2).
**Level of Maintenance**: actively maintained.

Expand Down
6 changes: 3 additions & 3 deletions mkdocs.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ nav:
- Architecture: architecture.md
- Selection:
- selection/index.md
- selection/monitoring.md
- selection/alerting.md
- selection/automation-and-tooling.md
- Monitoring: selection/monitoring.md
- Alerting: selection/alerting.md
- Automation and Tooling: selection/automation-and-tooling.md
- credit.md

extra_css:
Expand Down

0 comments on commit 7875233

Please sign in to comment.