Skip to content

Fix a few doc typos for hybrid node setup #1079

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

Merged
merged 3 commits into from
Aug 8, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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/nodes/hybrid-nodes-cni.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Cilium version `v1.16.x` is supported and recommended for EKS Hybrid Nodes for e

Calico version `v3.29.x` is supported and recommended for EKS Hybrid Nodes for every Kubernetes version supported in Amazon EKS.

See eks/latest/userguide/kubernetes-versions.html[Kubernetes version support,type="documentation"] for the Kubernetes versions supported by Amazon EKS. EKS Hybrid Nodes have the same Kubernetes version support as Amazon EKS clusters with cloud nodes.
See link:eks/latest/userguide/kubernetes-versions.html[Kubernetes version support,type="documentation"] for the Kubernetes versions supported by Amazon EKS. EKS Hybrid Nodes have the same Kubernetes version support as Amazon EKS clusters with cloud nodes.

== Supported capabilities

Expand Down
2 changes: 1 addition & 1 deletion latest/ug/nodes/hybrid-nodes-configure.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ EKS includes insight checks for misconfigurations in your EKS Hybrid Nodes setup

The following lists the add-ons and other components that have different configuration for hybrid nodes:

* *Container Networking Interface (CNI)*: The core capabilities of link:https://docs.cilium.io/en/stable/index.html[Cilium] and link:https://docs.tigera.io/calico/latest/about/[Calico] are supported for use with hybrid nodes. You can manage your CNI on hybrid nodeswith your choice of tooling such as Helm. The {aws} VPC CNI can't be used with hybrid nodes. For more information, see <<hybrid-nodes-cni>>.
* *Container Networking Interface (CNI)*: The core capabilities of link:https://docs.cilium.io/en/stable/index.html[Cilium] and link:https://docs.tigera.io/calico/latest/about/[Calico] are supported for use with hybrid nodes. You can manage your CNI on hybrid nodes with your choice of tooling such as Helm. The {aws} VPC CNI can't be used with hybrid nodes. For more information, see <<hybrid-nodes-cni>>.
* *CoreDNS and `kube-proxy`*: CoreDNS and `kube-proxy` are installed automatically when hybrid nodes join the EKS cluster. These add-ons can be managed as EKS add-ons after cluster creation.
* *Ingress and Load Balancing*: You can use the {aws} Load Balancer Controller and Application Load Balancer (ALB) or Network Load Balancer (NLB) with the target type `ip` for workloads on hybrid nodes connected with {aws} Direct Connect or {aws} Site-to-Site VPN. You can alternatively use your choice of Ingress controller or load balancer for application traffic that stays local to your on-premises environment.
* *Metrics*: You can use Amazon Managed Service for Prometheus (AMP) agent-less scrapers, {aws} Distro for Open Telemetry (ADOT), and the Amazon CloudWatch Observability Agent with hybrid nodes. To use AMP agent-less scrapers for pod metrics on hybrid nodes, your pods must be accessible from the VPC that you use for the EKS cluster.
Expand Down
1 change: 0 additions & 1 deletion latest/ug/nodes/hybrid-nodes-join.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,6 @@ The hybrid nodes CLI (`nodeadm`) must be run with a user that has sudo/root acce
[source,bash,subs="verbatim,attributes,quotes"]
----
nodeadm install [.replaceable]`K8S_VERSION` --credential-provider [.replaceable]`CREDS_PROVIDER`

----

== Step 3: Connect hybrid nodes to your cluster
Expand Down