Skip to content

Update instructions on external network #2511

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
ctauchen merged 2 commits into from
Feb 4, 2026
Merged

Update instructions on external network #2511

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
79ef817
Update instructions on external network
song-jiang Feb 4, 2026
a0598c2
Review Markups
song-jiang Feb 4, 2026
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
13 changes: 13 additions & 0 deletions calico-enterprise/networking/egress/external-network.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,19 @@ kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"externalNetworkSupport":"Enabled"}}'
```

### Configure egress interfaces

To configure which host interfaces should be used for egress traffic and have the `src_valid_mark` set, configure the `egressIPHostIfacePattern` field in the default **FelixConfiguration**. This field accepts a comma-separated list of interface names and/or regular expressions. Regular expressions must be wrapped in `/.../ `.

For example, to configure interfaces matching the pattern `ens20` or `ens21` with VLAN IDs 100 or 200:

```bash
kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"egressIPHostIfacePattern":"/^ens2[01][./](100|200)$/"}}'
```

This ensures that $[prodname] sets the `src_valid_mark` on interfaces matching the specified patterns, which is required for proper egress gateway functionality with external networks.

### Create external network resources

Add an `ExternalNetwork` resource to the cluster for each external networks. For example, to create an `ExternalNetwork` for `red` network.
Expand Down
13 changes: 13 additions & 0 deletions ...enterprise_versioned_docs/version-3.21-2/networking/egress/external-network.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,19 @@ kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"externalNetworkSupport":"Enabled"}}'
```

### Configure egress interfaces

To configure which host interfaces should be used for egress traffic and have the `src_valid_mark` set, configure the `egressIPHostIfacePattern` field in the default **FelixConfiguration**. This field accepts a comma-separated list of interface names and/or regular expressions. Regular expressions must be wrapped in `/.../ `.

For example, to configure interfaces matching the pattern `ens20` or `ens21` with VLAN IDs 100 or 200:

```bash
kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"egressIPHostIfacePattern":"/^ens2[01][./](100|200)$/"}}'
```

This ensures that $[prodname] sets the `src_valid_mark` on interfaces matching the specified patterns, which is required for proper egress gateway functionality with external networks.

### Create external network resources

Add an `ExternalNetwork` resource to the cluster for each external networks. For example, to create an `ExternalNetwork` for `red` network.
Expand Down
13 changes: 13 additions & 0 deletions ...enterprise_versioned_docs/version-3.22-2/networking/egress/external-network.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,19 @@ kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"externalNetworkSupport":"Enabled"}}'
```

### Configure egress interfaces

To configure which host interfaces should be used for egress traffic and have the `src_valid_mark` set, configure the `egressIPHostIfacePattern` field in the default **FelixConfiguration**. This field accepts a comma-separated list of interface names and/or regular expressions. Regular expressions must be wrapped in `/.../ `.

For example, to configure interfaces matching the pattern `ens20` or `ens21` with VLAN IDs 100 or 200:

```bash
kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"egressIPHostIfacePattern":"/^ens2[01][./](100|200)$/"}}'
```

This ensures that $[prodname] sets the `src_valid_mark` on interfaces matching the specified patterns, which is required for proper egress gateway functionality with external networks.

### Create external network resources

Add an `ExternalNetwork` resource to the cluster for each external networks. For example, to create an `ExternalNetwork` for `red` network.
Expand Down
13 changes: 13 additions & 0 deletions ...enterprise_versioned_docs/version-3.23-1/networking/egress/external-network.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,19 @@ kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"externalNetworkSupport":"Enabled"}}'
```

### Configure egress interfaces

To configure which host interfaces should be used for egress traffic and have the `src_valid_mark` set, configure the `egressIPHostIfacePattern` field in the default **FelixConfiguration**. This field accepts a comma-separated list of interface names and/or regular expressions. Regular expressions must be wrapped in `/.../ `.

For example, to configure interfaces matching the pattern `ens20` or `ens21` with VLAN IDs 100 or 200:

```bash
kubectl patch felixconfiguration default --type='merge' -p \
'{"spec":{"egressIPHostIfacePattern":"/^ens2[01][./](100|200)$/"}}'
```

This ensures that $[prodname] sets the `src_valid_mark` on interfaces matching the specified patterns, which is required for proper egress gateway functionality with external networks.

### Create external network resources

Add an `ExternalNetwork` resource to the cluster for each external networks. For example, to create an `ExternalNetwork` for `red` network.
Expand Down