iptables

Documentation

Overview

Package iptables manages iptables-related configuration for Cilium.

Index

• type IptablesManager
  • func (m *IptablesManager) Init()
  • func (m *IptablesManager) InstallProxyRules(proxyPort uint16, ingress bool, name string) error
  • func (m *IptablesManager) InstallRules(ifName string) error
  • func (m *IptablesManager) RemoveProxyRules(proxyPort uint16, ingress bool, name string) error
  • func (m *IptablesManager) RemoveRules()
  • func (m *IptablesManager) TransientRulesEnd()
  • func (m *IptablesManager) TransientRulesStart(ifName string) error

Types

type IptablesManager

type IptablesManager struct {
	// contains filtered or unexported fields
}

IptablesManager manages the iptables-related configuration for Cilium.

func (*IptablesManager) Init

func (m *IptablesManager) Init()

Init initializes the iptables manager and checks for iptables kernel modules availability.

func (*IptablesManager) InstallProxyRules

func (m *IptablesManager) InstallProxyRules(proxyPort uint16, ingress bool, name string) error

func (*IptablesManager) InstallRules

func (m *IptablesManager) InstallRules(ifName string) error

InstallRules installs iptables rules for Cilium in specific use-cases (most specifically, interaction with kube-proxy).

func (*IptablesManager) RemoveProxyRules

func (m *IptablesManager) RemoveProxyRules(proxyPort uint16, ingress bool, name string) error

func (*IptablesManager) RemoveRules

func (m *IptablesManager) RemoveRules()

RemoveRules removes iptables rules installed by Cilium.

func (*IptablesManager) TransientRulesEnd

func (m *IptablesManager) TransientRulesEnd()

TransientRulesEnd removes Cilium related rules installed from TransientRulesStart.

func (*IptablesManager) TransientRulesStart

func (m *IptablesManager) TransientRulesStart(ifName string) error

TransientRulesStart installs iptables rules for Cilium that need to be kept in-tact during agent restart which removes/installs its main rules. Transient rules are then removed once iptables rule update cycle has completed. This is mainly due to interactions with kube-proxy.