Skip to content

Commit 78a2d75

Browse files
fix: Correct grammar in Markdown files (#18)
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
1 parent 910fa7b commit 78a2d75

File tree

1 file changed

+12
-13
lines changed

1 file changed

+12
-13
lines changed

README.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ clusters across multiple cloud accounts, using GitOps principles with ArgoCD.
66
## Requirements
77

88
Guides on setting up Kubernetes clusters in the cloud are common, but few cover
9-
managing clusters across multiple providers and accounts (a key need for large
10-
enterprises)
9+
managing clusters across multiple providers and accounts, a key need for large
10+
enterprises.
1111

1212
This project aims to provide a practical example:
1313

@@ -30,15 +30,15 @@ Each cloud provider has a designated "management account" where subdomains are h
3030
> The second-level domain `mylabs.dev` is hosted externally (e.g., Cloudflare),
3131
> and it's the user's responsibility to configure DNS delegation properly.
3232
33-
An IAM role (or the equivalent for each cloud provider) will be created in the
34-
management account. This role will allow GitHub Actions / mise to manage resources
33+
An IAM role (or its equivalent for each cloud provider) will be created in the
34+
management account. This role will allow GitHub Actions/mise to manage resources
3535
in the management account and will also be used to access other accounts where
3636
Kubernetes clusters are deployed.
3737

3838
## Cloud Providers - Multi-Account Setup
3939

40-
Let's assume you have 2 AWS accounts, 2 Azure accounts, 2 GCP accounts and you
41-
want to deploy 2 Kubernetes clusters (EKS, AKS, GKE) in each account:
40+
Let's assume you have two AWS accounts, two Azure accounts, and two GCP accounts,
41+
and you want to deploy two Kubernetes clusters (EKS, AKS, GKE) in each account:
4242

4343
| Cloud Provider | Account 01 | Account 02 |
4444
|--------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|
@@ -79,17 +79,16 @@ AWS_USER_ARN=$(aws iam list-users --query "Users[? UserName==\`${AWS_USER_NAME}\
7979
sed -i "s@^AWS_USER_ARN.*@AWS_USER_ARN = \"${AWS_USER_ARN}\"@" mise.local.toml
8080
```
8181

82-
The `aws-cli` user was created in the management AWS account. It will be used to
83-
access all AWS accounts via the AWS CLI by assuming the proper IAM Role.
82+
The `aws-cli` user is created in the management AWS account. It will be used to
83+
access all AWS accounts via the AWS CLI by assuming the proper IAM role.
8484

8585
##### Route35 Hosted Zone + GitHub Action IAM Role
8686

8787
The following steps will create a Route 53 hosted zone for the subdomain
88-
`aws.mylabs.dev` and a GitHub Action IAM role that can be assumed by the
88+
`aws.mylabs.dev` and a GitHub Actions IAM role that can be assumed by the
8989
GitHub Actions workflow.
90-
The GitHub Action IAM role will be used to manage resources in the management
91-
account and will also be used to access other accounts where Kubernetes
92-
clusters are deployed.
90+
The GitHub Actions IAM role will be used to manage resources in the management
91+
account and to access other accounts where Kubernetes clusters are deployed.
9392

9493
Create a Route 53 hosted zone for `aws.mylabs.dev`:
9594

@@ -127,7 +126,7 @@ mise run create:aws-tenant:cf-iam-role
127126

128127
## K8s Clusters
129128

130-
All the "kubeconfig files" will be stored in the `clusters/.kubeconfigs`
129+
All kubeconfig files will be stored in the `clusters/.kubeconfigs`
131130
directory.
132131

133132
### Kind

0 commit comments

Comments
 (0)