Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pod identity update #1026

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

pod identity update #1026

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5daf4db
pod identity update
jessegoodier May 3, 2024
4dac060
Merge branch 'main' into pod-identity2
chipzoller Feb 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 35 additions & 26 deletions ...ll/cloud-integration/aws-cloud-integrations/aws-cloud-integration-using-irsa.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -209,9 +209,42 @@ eksctl utils associate-iam-oidc-provider \
--approve
```

**Linking default Kubecost Service Account to an IAM Role**
**Use IAM Role with the Kubecost Service Account**

Kubecost's default service account `kubecost-cost-analyzer` is automatically created in the `kubecost` namespace upon installation. This service account can be linked to an IAM Role via Annotation + IAM Trust Policy.
Kubecost's default service account `kubecost-cost-analyzer` is automatically created in the namespace that it is installed to. This service account needs to use the IAM Role created earlier.

There are 3 ways to use the IAM Role with the Kubecost Service Account:

1. EKS Pod Identity - likely the easiest and is recommended (6a)
2. Create a new dedicated service account for Kubecost (6b)
3. Use an existing service account for Kubecost (6c)


### Step 6a: EKS Pod Identity

{% hint style="warning" %}
Your cluster must support [EKS Pod Identities](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html) to use the method below.
This is supported as of Kubecost 2.2.2
{% endhint %}

Create your pod identity association:

```sh
eksctl create podidentityassociation \
--cluster $CLUSTER_NAME --region $AWS_REGION \
--namespace kubecost \
--service-account-name kubecost-serviceaccount \
--role-name kubecost-serviceaccount \
--permission-policy-arns arn:aws:iam::SUB_ACCOUNT_222222222:policy/kubecost-access-cur-in-payer-account
```

Then update your *values.yaml* file:

```yaml
serviceAccount:
create: true
name: kubecost-serviceaccount
```

In the Helm values for your deployment, add the following section:

Expand Down Expand Up @@ -273,30 +306,6 @@ serviceAccount:
name: kubecost-serviceaccount
```

### Step 6 (optional): Setting up EKS Pod Identity

{% hint style="warning" %}
Your cluster must support [EKS Pod Identities](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html) to use the method below.
{% endhint %}

Create your pod identity association:

```sh
eksctl create podidentityassociation \
--cluster $CLUSTER_NAME --region $AWS_REGION \
--namespace kubecost \
--service-account-name kubecost-serviceaccount \
--role-name kubecost-serviceaccount \
--permission-policy-arns arn:aws:iam::SUB_ACCOUNT_222222222:policy/kubecost-access-cur-in-payer-account
```

Then update your *values.yaml* file:

```yaml
serviceAccount:
create: true
name: kubecost-serviceaccount
```

## Validation

Expand Down
Loading