README.md

Kubecost AWS Deployment Guide (Self-hosted)

It is recommended to deploy Kubecost Enterprise in this order to improve time to value. Configuring the AWS cloud integration will provide the most accurate data. Otherwise, it will default to on-demand public pricing and will not accurately reflect your AWS bill.

Prerequisites

A total of 3 buckets are required in order to support a IBM Kubecost Federated deployment with AWS cloud integration.

1. • Generate AWS CUR
2. • Set up a dedicated s3 object store for cluster metrics
   • Create storage policy
3. • Set up a dedicated s3 object store for athena query results
   • Create storage policy based on set up

Kubecost Installation - Choose appropriate option.

1. Kubecost Installed on Primary Cluster

   Option A: Enterprise with IRSA/EKS Pod Identities

   • Enteprise Federation with IRSA/EKS Pod Identities

   helm upgrade --install kubecost \
     --repo https://kubecost.github.io/kubecost/ kubecost \
     --namespace kubecost \
     -f aws-primary-federation-irsa.yaml

• Verify ETL pipeline is working by checking that a /federated directory was created in the object-store. If no /federated directory exists, double check configuration, finops-agent pod logs or test that the user can curl the bucket endpoint from inside the finops-agent container.

Option B: Using Access Key and Secret

• Enteprise Federation no IRSA

   helm upgrade --install kubecost \
     --repo https://kubecost.github.io/kubecost/ kubecost \
     --namespace kubecost \
     -f aws-primary.yaml

2. Cloud Cost Integration Configured

   • AWS Cloud Integration

   • AWS Cloud Integration using IRSA/EKS Pod Identities

   • Cloud Integration Config File

3. Kubecost Installed on Secondary Cluster(s)

   Option A: With IRSA/EKS Pod Identities

   • ETL Federation Aggregator Configuration with IRSA

   helm upgrade --install kubecost \
     --repo https://kubecost.github.io/kubecost/ kubecost \
     --namespace kubecost \
     -f aws-kubecost-agent-irsa.yaml

Option B: Using Access Key and Secret

• ETL Federation Aggregator Configuration no IRSA

   helm upgrade --install kubecost \
     --repo https://kubecost.github.io/kubecost/ kubecost \
     --namespace kubecost \
     -f aws-kubecost-agent.yaml

Optional Configuration

4. Network Costs Daemonset Configured

Please Note: The network cost daemonset will experience CPU throttling and higher memory consumption in large environments where there are several hundred thousand or more unique containers running per day.

• Review Configuration Guide
• Apply Network Cost Config

5. Kubecost Actions

Continuous Container Requst Right-sizing & Resource Quota Right-sizing

⚠️Important Note: In order to use this feature, users must obtain a v3 license key. Reach out to your Account Representative(s)

helm upgrade --install kubecost \
     --repo https://kubecost.github.io/kubecost/ kubecost \
     --namespace kubecost \
     -f https://raw.githubusercontent.com/kubecost/kubecost-success/refs/heads/main/actions-primary.yaml

6. SSO/SAML Enabled
   • Review SSO Documentation
   • Configure OIDC
   • Configure SAML

Troubleshooting

Common issues and their solutions will be documented here.

References

• Kubecost Documentation
• Helm Chart Reference
• Support Resources