Skip to content

Commit

Permalink
improve the doc changes
Browse files Browse the repository at this point in the history
  • Loading branch information
jeswinkoshyninan committed May 14, 2024
1 parent 22b2e6b commit 7b3f80d
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/deploy/configurations.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Currently, you can set only 1 namespace to watch in this flag. See [this Kuberne
| aws-max-retries | int | 10 | Maximum retries for AWS APIs |
| aws-region | string | [instance metadata](#instance-metadata) | AWS Region for the kubernetes cluster |
| aws-vpc-id | string | [instance metadata](#instance-metadata) | AWS VPC ID for the Kubernetes cluster |
| aws-vpc-tags | stringMap | | Tags for the Kubernetes cluster VPC, Note that if both flags --aws-vpc-id and --aws-vpc-tags are specified, the controller uses the value in --aws-vpc-id to fetch the VPC info and ignores the other flag.
| aws-vpc-tags | stringMap | | Tags for the Kubernetes cluster VPC, When both flags `--aws-vpc-id` and `--aws-vpc-tags` are specified, the controller prioritizes `--aws-vpc-id` and ignores the other flag.
| aws-vpc-tag-key | string | Name | Optional tag key used with aws-vpc-tags add only if VPC name tag key is not the default value "Name"
| allowed-certificate-authority-arns | stringList | [] | Specify an optional list of CA ARNs to filter on in cert discovery (empty means all CAs are allowed) |
| backend-security-group | string | | Backend security group id to use for the ingress rules on the worker node SG |
Expand Down
2 changes: 1 addition & 1 deletion docs/deploy/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ You can set the IMDSv2 as follows:
aws ec2 modify-instance-metadata-options --http-put-response-hop-limit 2 --http-tokens required --region <region> --instance-id <instance-id>
```

Instead of depending on IMDSv2, you can specify the AWS Region via the controller flag `--aws-region`, and the AWS VPC via controller flag `--aws-vpc-id` or by specifying vpc tags via the flag `--aws-vpc-tags` and an optional flag `--aws-vpc-tag-key` if you have a different key for the tag other than "Name". Note that if you specify flags `--aws-vpc-id` and `--aws-vpc-tags`, then value given to `--aws-vpc-id` will be taken by controller.
Instead of depending on IMDSv2, you can specify the AWS Region via the controller flag `--aws-region`, and the AWS VPC via controller flag `--aws-vpc-id` or by specifying vpc tags via the flag `--aws-vpc-tags` and an optional flag `--aws-vpc-tag-key` if you have a different key for the tag other than "Name". When both flags `--aws-vpc-id` and `--aws-vpc-tags` are specified, the controller prioritizes `--aws-vpc-id`and ignores the other flag.

## Configure IAM

Expand Down

0 comments on commit 7b3f80d

Please sign in to comment.