Brand
  • v3.5
    • v3.5 (latest)
    • v3.4
    • v3.3
    • v3.2
    • v3.1
    • v3.0
    • v2.6
    • nightly
  • Home
  • Resources
    •   Getting Started
    •   Documentation
    •   Videos & Webinars
    •   Training
    •   Releases
    •   Blog
  • Community
    •   Slack
    •   Upcoming Events
    •   Newsletter
    •   GitHub
    •   Jobs
    •   Blog
  • Support
  • Tigera
  • Introduction
  • Getting Started
  • Usage
  • Reference
  • Releases
  • Introduction
  • Getting Started
  • Usage
  • Reference
  • Releases

Using Calico
calicoctl
Installing calicoctl
Configuring calicoctl
Overview
etcd datastore options
Kubernetes API datastore options
Securing Calico component communications
Scheduling to well-known nodes
Configuring encryption and authentication
Securing Calico's Prometheus endpoints
Running calico/node with an init system
Configuring BGP Peers
Changing IP Pools
Route Reflectors
Enabling IPv6 Support
Enabling IPVS in Kubernetes
External Connectivity
Configuring IP-in-IP
Configuring a Node IP Address and Subnet
Configuring MTU
Decommissioning a Node
Configuring Conntrack
Advertising Kubernetes services
Assigning IP addresses based on topology
Calico for OpenStack
Endpoint Labels
Configuration
Detailed Semantics
Floating IPs
Service IPs
Host routes
Kuryr
Troubleshooting
Logging
Frequently Asked Questions
Edit this page

Configuring Conntrack

A common problem on Linux systems is running out of space in the conntrack table, which can cause poor iptables performance. This can happen if you run a lot of workloads on a given host, or if your workloads create a lot of TCP connections or bidirectional UDP streams.

To avoid this becoming a problem, we recommend increasing the conntrack table size. To do so, run the following commands:

sysctl -w net.netfilter.nf_conntrack_max=1000000 
echo "net.netfilter.nf_conntrack_max=1000000" >> /etc/sysctl.conf
Provide Feedback Get Help via Slack Training