diff --git a/latest/ug/nodes/hybrid-nodes-cni.adoc b/latest/ug/nodes/hybrid-nodes-cni.adoc index 90b04a7e..af03df21 100644 --- a/latest/ug/nodes/hybrid-nodes-cni.adoc +++ b/latest/ug/nodes/hybrid-nodes-cni.adoc @@ -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 diff --git a/latest/ug/nodes/hybrid-nodes-configure.adoc b/latest/ug/nodes/hybrid-nodes-configure.adoc index ba2b9fc6..c2317451 100644 --- a/latest/ug/nodes/hybrid-nodes-configure.adoc +++ b/latest/ug/nodes/hybrid-nodes-configure.adoc @@ -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 <>. +* *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 <>. * *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. diff --git a/latest/ug/nodes/hybrid-nodes-join.adoc b/latest/ug/nodes/hybrid-nodes-join.adoc index 95426846..9e5cb39e 100644 --- a/latest/ug/nodes/hybrid-nodes-join.adoc +++ b/latest/ug/nodes/hybrid-nodes-join.adoc @@ -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