Skip to content

fix: fixed incorrect command for "Step 6: Scale down CoreDNS" #1082

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
geoffcline merged 2 commits into from
Aug 8, 2025
Merged

fix: fixed incorrect command for "Step 6: Scale down CoreDNS" #1082

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e20015
fix: fixed incorrect command for "Step 6: Scale down CoreDNS"
ClarenceBai Aug 5, 2025
bc91c02
fix: fixed spelling issue
ClarenceBai Aug 5, 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
2 changes: 1 addition & 1 deletion latest/ug/automode/auto-migrate-fargate.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,5 +237,5 @@ Because EKS Auto mode handles CoreDNS, you scale the `coredns` deployment down t

[source,bash,subs="verbatim,attributes"]
----
kubectl scale deployment coredns -n kube-system —replicas=0
kubectl scale deployment coredns -n kube-system —-replicas=0
----
2 changes: 1 addition & 1 deletion latest/ug/automode/create-node-class.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,7 +213,7 @@ spec:
== Considerations

* If you want to verify how much local storage an instance has, you can describe the node to see the ephemeral storage resource.
* *Volume Encryption* - EKS users the configued custom KMS key to encrypt the read-only root volume of the instance and the read/write data volume.
* *Volume Encryption* - EKS uses the configured custom KMS key to encrypt the read-only root volume of the instance and the read/write data volume.
* *Replace the node IAM role* - If you change the node IAM role associated with a `NodeClass`, you will need to create a new Access Entry. EKS automatically creates an Access Entry for the node IAM role during cluster creation. The node IAM role requires the `AmazonEKSAutoNodePolicy` EKS Access Policy. For more information, see <<access-entries>>.
* *maximum pod density* - EKS limits the maximum number of pods on a node to 110. This limit is applied after the existing max pods calculation. For more information, see <<choosing-instance-type>>.
* *Tags* - If you want to propagate tags from Kubernetes to EC2, you need to configure additional IAM permissions. For more information, see <<auto-learn-iam>>.
Expand Down