Skip to content
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

docs: update cilium parameter descriptions and agent mode steps for EKS Hybrid Nodes #5605

Merged
merged 4 commits into from
Jan 30, 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
Original file line number Diff line number Diff line change
Expand Up @@ -37,13 +37,10 @@ You must then configure your networking to allow traffic to reach the pods on yo

5. Select **Edge Native** from the **Infrastructure provider** list, and click **Next**.

6. Select your base OS pack depending on how you will register your edge hosts.
6. Select **BYOS - Edge OS** as your base OS pack.

- For Agent Mode, select **BYOS - Agent Mode**.
- For Appliance Mode, select **BYOS - Edge OS**.

7. If selecting **BYOS - Agent Mode**, on the **Configure Pack** page, click **Values** under **Pack Details**. Then,
click on **Presets** on the right-hand side, and select **Agent Mode**.
7. If using [Agent Mode](../../../../deployment-modes/agent-mode/agent-mode.md), on the **Configure Pack** page, click
**Values** under **Pack Details**. Then, click on **Presets** on the right-hand side, and select **Agent Mode**.

8. Click **Next layer** to continue.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -369,16 +369,18 @@ Cilium handles IP Address Management (IPAM) and Border Gateway Protocol (BGP) fo

8. For **IPAM mode**, select **Cluster Pool**.

9. In the YAML editor, search for **clusterPoolIPv4PodCIDRList**. This parameter specifies the overall IP ranges
available for pod networking across all your hybrid nodes.
9. In the YAML editor, search for **clusterPoolIPv4PodCIDRList**. This parameter specifies the CIDR ranges from which
pod IPs will be allocated across all your hybrid nodes.

Adjust the pod CIDR list for hybrid pods in other networks that need to connect to this cluster. For example,
`192.168.0.0`.
Adjust the pod CIDR list for hybrid pods in other networks that need to connect to this cluster. This should match
the **Remote Pod CIDRs** value defined in step 11 during the [Import Cluster](#import-cluster) steps. For example,
`192.168.0.0/16`.

10. In the YAML editor, search for **clusterPoolIPv4MaskSize**. This parameter determines the subnet mask size used for
pod IP allocation within each hybrid node.
10. In the YAML editor, search for **clusterPoolIPv4MaskSize**. This parameter defines the size of each per-node CIDR
block.

Adjust the mask size based on your required pods per hybrid node. For example, `/25`.
Adjust the mask size based on your required pods per hybrid node. For example, `/25` would provides 126 usable pod
IPs for each node.

11. In the Presets, find the **cilium-agent - Hybrid Nodes Affinity** option, and select **Amazon EKS**.

Expand Down