Releases: F5Networks/f5-cloud-failover-extension
Releases · F5Networks/f5-cloud-failover-extension
v1.13.0
Features added:
- Issue #103: Added support for Serverside Encryption on the S3 Bucket using Amazon S3-Managed Keys (SSE-S3) or KMS keys Stored in AWS Key Management Service (SSE-KMS) with either the default AWS managed key or a customer managed key.
Bugs fixed:
- Fixed Issue #96 which prevented explicit configuration with addressGroupDefinitions from working.
Documentation:
- Updated documentation. See the documentation revision history for more information.
v1.12.0
Bugs fixed:
- Fixed issue where failover does not correctly check traffic group status in recovery mode.
v1.11.0
Features added:
- Added support for custom Azure environments.
- Users can now validate their deployment by seeing more objects discovered by CFE with "/inspect", including NICs, IP addresses, Routes/RouteTables, etc.
Bugs fixed:
- Fixed Issue #94 which prevented explicit configuration with addressGroupDefinitions from working for AWS Same Net.
Documentation:
- Updated documentation. See the documentation revision history for more information.
v1.10.0
New Features:
- Support IPV6 Route Failover for Azure cloud.
- Support for AWS IMDSv2.
- Enhanced logging to provide better visibility into Azure Route failover.
- Updated TEEM payload with additional information.
Bugs Fixed:
- Fixed Issue #74 which causes GCP Failover for Alias Address to fail when no forwarding rules are configured.
- Fixed Issue #75 which causes CFE failure in AWS if an unused IPv6 address is listed in Virtual Addresses.
- Fixed Issue #76 which causes IPv6 addresses in AWS to only fail over if IPv4 addresses exist too.
- Fixed Issue #79 which made CFE failover incorrectly count IPv6 addresses per interface in AWS IPv6 failover.
- Fixed Issue #80 which crashes CFE when it receives an error message from AWS during failover.
- Enhanced trigger.sh script to prevent curl command hangs.
- Resolved security vulnerabilities reported by NPM audit.
- Adjusted retries logic to mitigate the situation when LX Framework returns generic 400 error (i.e. {"code":400,"message":"remoteSender:Unknown, method:POST ","referer":"Unknown","restOperationId":1984130,"kind":":resterrorresponse"} ).
- Fixed the problem with "addressGroupDefinitions" for Azure cloud when only single address gets updated.
Documentation:
- Updated documentation with new TEEM payload.
- Documentation is continuously updated on CloudDocs.f5.com. See the documentation revision history for specific changes.
v1.9.0
Bugs Fixed:
- Fixed Issue #64 which caused secondary IP addresses to be deleted in CFE declarations for AWS.
Documentation:
- Added notes to documentation related to Issue #66.
- Fixed a broken link related to Issue #28.
- Documentation is continuously updated on CloudDocs.f5.com. See the documentation revision history for specific changes.
v1.8.0
New Features:
- Improved performance of updateAddress function and added a new discoverAddresses method.
Bugs Fixed:
- Resolved dependency vulnerabilities.
- Fixed an issue that caused CFE to fail in GCP environments with the following error message: "Cannot read property 'length' of undefined."
Documentation:
- Documentation is continuously updated on CloudDocs.f5.com. See the documentation revision history for specific changes.
v1.7.1
v1.7.0
New Features:
- Added specific config options so that users may now explicitly provide the names, IDs, and mappings of resources in the CFE configuration as an alternative to discovery-based functionality. This feature helps speed up failover.
- Added more description logging for Forward Rules and Target Instances to help with troubleshooting.
- Added support for failover of IPv6 addresses in AWS. This fixes issue #49.
Bugs Fixed:
- Fixed issue #27.
- Fixed an issue that caused CFE to fail in instances where two or more objects are configured on BIG-IP with the same IP address.
- Fixed a vulnerability involving date-and-time.
- Resolved incorrect error condition when locating target instances.
Documentation:
- Added a new section covering CFE in Isolated Environments.
v1.6.1
v1.6.0
New Features:
- Added property requireScopingTags for GCP forwarding rules. See the documentation for more information.
- Issue #31: Added ability to see missing objects and how it affects failover.
- Added a configurable interval for public cloud failover recovery.
- Added ability for CFE to make API requests via proxy.
Bugs Fixed:
- Fixed issue #8 that caused CFE to only update forwarding rules based on IP. Port numbers are now included in the scoping range.
- Fixed issue #24 by adding a warning to the API documentation for users not to use execute function on the /trigger endpoint.
- Fixed issue #32 that caused CFE on Google Cloud Platform to move only aliasIP ranges associated with NIC0. CFE now moves aliasIP on other NICs.
- Fixed security vulnerabilities related to node-forge.
Documentation:
- Added a separate section for AWS same availability zones use cases.
- Added GCP to the Performance and Sizing section of Clouddocs.
- Updated the section for Tagging the User-Defined Routes in Azure.
- Documentation is continuously updated on CloudDocs.f5.com. See the documentation revision history for specific changes.