v0.9.0

What's Changed

• [agent] Adjust policy handling for IPv6 addresses by @sstrk in #57
• Do not generate nftables chains for network policies if FilterTableName is empty by @ibot3 in #55

Full Changelog: v0.8.0...v0.9.0

v0.8.0

What's Changed

• Fix incompatibility with OVN-based clouds by @tschuettig in #54

New Contributors

• @tschuettig made their first contribution in #54

Full Changelog: v0.7.0...v0.8.0

Feature release 0.7.0

• Improve scoping of actions within OpenStack (#51). Previously, if the credentials allowed listing of ports or floating IPs outside the current project, those would also be affected. This is generally only the case with OpenStack admin credentials which you aren't supposed to use anyway.
• Update all dependencies and bump golang version to 1.21.3.

Feature release 0.6.0

• Add support for running outside OpenStack (#41), with focus on VyOS-based routers as gateways. This brings a new port manager (which uses static IP address management) in the controller as well as partial nftables reload and SNAT-free forwarding in the agent.

Feature release 0.5.0

• Add support for NetworkPolicy objects. Network policies which affect the pods belonging to your service now also apply to the load balancer ingress. If you use network policies and do not allow any CIDRs, no external traffic will be accepted (#36)

Bugfix release 0.4.2

• Fix loss of IP addresses due to a race condition in the work queue (#30, PR #33)

Bugfix release 0.4.1

• Fix another potential cause of confusion in the IP address management (pull #29; mind to check the commit messages, the PR description is not where it's at)

Update release 0.4.0

• All dependencies are bumped to the most recent version
• Removed the port cache in order to avoid issues with cache invalidation

Bugfix release 0.3.3

• Fix incorrect nftables rules in dualstack clusters (#25, PR #26). Previously, in dual stack clusters, the IPv6 addresses would be added to the IPv4 destination map in nftables, causing nftables to fail to load.

Bugfix release 0.3.2

• Attempt at fixing the agent confusing itself under some circumstances, losing floating IPs (#24).