Skip to content

Clarify secret naming in EKS Fargate sidecar injection doc #19871

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

Merged
merged 3 commits into from
Apr 1, 2025
Merged

Clarify secret naming in EKS Fargate sidecar injection doc #19871

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6fc2561
Clarify secret naming in EKS Fargate sidecar injection doc
levan-m Mar 18, 2025
2995fe8
Update eks_fargate/README.md
levan-m Mar 31, 2025
7559de7
Update eks_fargate/README.md
levan-m Mar 31, 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
8 changes: 6 additions & 2 deletions eks_fargate/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ The setup below configures the Cluster Agent to communicate with the Agent sidec

* Set up RBAC in the application namespace(s). See the [AWS EKS Fargate RBAC](#aws-eks-fargate-rbac) section on this page.
* Bind above RBAC to application pod by setting Service Account name.
* Create a Kubernetes secret containing your Datadog API key and Cluster Agent token in the Datadog installation and application namespaces:
* Create a Kubernetes secret `datadog-secret` containing your Datadog API key and Cluster Agent token in the Datadog installation and application namespaces:

```shell
kubectl create secret generic datadog-secret -n datadog-agent \
Expand All @@ -131,6 +131,8 @@ The setup below configures the Cluster Agent to communicate with the Agent sidec
```
For more information how these secrets are used, see the [Cluster Agent Setup][35].

**Note**: You cannot change the name of the secret containing the Datadog API key and Cluster Agent token. It must be `datadog-secret` for the Agent in the sidecar to connect to Datadog.

###### Setup

1. Create a `DatadogAgent` custom resource in the `datadog-agent.yaml` with Admission Controller enabled:
Expand Down Expand Up @@ -293,7 +295,7 @@ The setup below configures the Cluster Agent to communicate with the Agent sidec

* Set up RBAC in the application namespace(s). See the [AWS EKS Fargate RBAC](#aws-eks-fargate-rbac) section on this page.
* Bind above RBAC to application pod by setting Service Account name.
* Create a Kubernetes secret containing your Datadog API key and Cluster Agent token in the Datadog installation and application namespaces:
* Create a Kubernetes secret `datadog-secret` containing your Datadog API key and Cluster Agent token in the Datadog installation and application namespaces:

```shell
kubectl create secret generic datadog-secret -n datadog-agent \
Expand All @@ -303,6 +305,8 @@ The setup below configures the Cluster Agent to communicate with the Agent sidec
```
For more information how these secrets are used, see the [Cluster Agent Setup][35].

**Note**: You cannot change the name of the secret containing the Datadog API key and Cluster Agent token. It must be `datadog-secret` for the Agent in the sidecar to connect to Datadog.

###### Setup

1. Create a file, `datadog-values.yaml`, that contains:
Expand Down
Loading