Releases: metal-stack/firewall-controller
Releases · metal-stack/firewall-controller
v2.0.0
v2.0.0-rc.1
v1.3.0
Required Actions
All firewalls of the infrastructure should be updated to version v1.3.0 of the firewall-controller. It will be the last version before the release of firewall-controller v2, which introduces the firewall-controller-manager. Rolling updates of firewall machines do not function with versions prior to this release, leaving the cluster in a state with unstable external network connection and two firewalls.
General Changes
v1.3.0-rc.1
v1.2.2
v1.2.1
General Changes
- bump metal-networker (#132) @GrigoriyMikhalkin
- updated README with DNS based egress policies examples (#129) @GrigoriyMikhalkin
v1.2.0
General Changes
- DNS based egress policies (#82) @GrigoriyMikhalkin
- Use refactored networker (#124) @majst01
- Update stern repo URL (#125) @peterfromthehill
v1.1.5
v1.1.4
General Changes
- update metal-networker to v0.8.3 (#120) @mwennrich
- fix gcloud action (#119) @majst01
- check if port is between 0 and 65535 (#116) @mwennrich
v1.1.3
General Changes
- Update controller-runtime, kube-builder, go, alpine and all dependencies, support port-ranges (#115) @majst01
- firewall-controller actual version stored in status (#114) @GrigoriyMikhalkin
- render temp nft-rule-file with leading dot (#112) @mwennrich
- added -v flag to show version (#113) @GrigoriyMikhalkin