-
Notifications
You must be signed in to change notification settings - Fork 5
CH-189 docs for cluster configuration #802
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.
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
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Adds and refines documentation and default Kubernetes configurations for cluster provisioning across GCP, AWS, and Azure, plus a bootstrap script.
- Rename and standardize GCP StorageClass and introduce an AWS default StorageClass.
- Provide AWS-specific ingress Helm values and update the cluster-init script to install ingress-nginx and cert-manager.
- Add detailed provider setup guides (GCP, AWS, Azure) and link them from the main README.
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| infrastructure/cluster-configuration/storageclass.yaml | Rename GCP StorageClass to standard with Delete policy |
| infrastructure/cluster-configuration/storageclass-default-aws.yaml | Add default AWS StorageClass configuration |
| infrastructure/cluster-configuration/ingress/values-aws.yaml | Add AWS NLB annotations and NGINX proxy cache settings |
| infrastructure/cluster-configuration/gcp-setup.md | Add quickstart GKE setup instructions |
| infrastructure/cluster-configuration/cluster-init.sh | Enhance bootstrap script with ingress-nginx and cert-manager |
| infrastructure/cluster-configuration/azure-setup.md | Add AKS/AGIC setup guide and conditional ingress template |
| infrastructure/cluster-configuration/aws-setup.md | Add EKS cluster creation and AWS Load Balancer Controller steps |
| infrastructure/cluster-configuration/README.md | Expand README with TLDR and provider-specific links |
| docs/build-deploy/cluster-configuration.md | Introduce high-level cluster configuration overview |
| --set crds.enabled=true | ||
|
|
||
|
|
||
| helm install --name cert-manager --namespace cert-manager --version v0.14.0 jetstack/cert-manager --set webhook.enabled=false |
Copilot
AI
May 22, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two separate helm install commands for cert-manager with differing versions and syntax; this will cause conflicts. Consolidate into a single, consistent installation.
| --set crds.enabled=true | |
| helm install --name cert-manager --namespace cert-manager --version v0.14.0 jetstack/cert-manager --set webhook.enabled=false | |
| --set crds.enabled=true \ | |
| --set webhook.enabled=false |
| Note that have to pay attention to the version of the aws-load-balancer-controller to match with the policy. Wrong version will make things fail | ||
|
|
||
| ```bash | ||
| curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/main/docs/install/iam_policy.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The IAM policy should not use main by default, but rather should be the version of the controller installed, eg: https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/**v2.13.2**/docs/install/iam_policy.json Similarly, a specific controller version, compatible with the policy should be installed.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Alex <alxbrd@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Closes CH-189