Releases: F5Networks/f5-cloud-failover-extension
Releases · F5Networks/f5-cloud-failover-extension
v2.1.3
Bugs Fixed:
- Fixed an issue where Azure resouce manager endpoints were missing a trailing slash, resulting in a "getaddrinfo ENOTFOUND" error in the CFE logs. Fixes GitHub Issue #141
v2.1.2
Bugs Fixed:
- Fixed an issue where failover fails when no Elastic IPs are configured in AWS
- Fixed an issue where dry run fails when failoverAddresses block is disabled or not present
v2.1.1
Bugs Fixed:
- Fixed an issue where connections to the Azure storage account failed when using a proxy server. Fixes GitHub Issue #141
v2.1.0
Features added:
- Added support for providing a fully-qualified virtual host-style S3 bucket name for the external storage scopingName. Addresses GitHub Issue #134
Bugs Fixed:
- Fixed an issue where BIG-IP proxy settings were not applied on initial requests to the external storage resource. Fixes GitHub Issue #138
- Fixed an issue with the Azure provider where requests to the failover state file would fail if there was more than one container in the storage account. Fixes GitHub Issue #137
- Fixed an issue with the Azure provider where error messages were not correctly logged.
Documentation:
- Updated FAQ to reflect that failover addresses in non-default route domains are not supported. Addresses GitHub Issue #139
v2.0.2
Bugs Fixed:
- Fixed an issue that caused Google storage bucket discovery to fail.
v2.0.1
Bugs Fixed:
- Fixed an issue that caused downloading the state file from Google storage to fail.
v2.0.0
Features added:
- Removed all dependencies on cloud provider SDK libraries; CFE now uses Axios to make cloud API requests.
- Simplified dry run output to omit extraneous information; AWS dry run output now includes the projected route next hop IP address.
- The AWS S3 storage bucket can now exist in a different region from the BIG-IP instances.
- The Azure storage provider now uses RBAC permissions to read/write failover state file, instead of using the storage account access key.
- Reduced RPM artifact size from 30 MB to 6 MB.
Documentation:
- Updated dry run troubleshooting section to reflect the new output format.
- Updated Azure role definition permissions list to reflect required storage account permissions.
v1.15.0
Features added:
- Updated logging to correctly reflect task status when no public IP address operations are discovered.
Bugs Fixed:
- Fixed issue where an AWS private IP address was not returned in an /inspect response if the private address was not associated with an Elastic IP Address. Fixes GitHub Issue #114.
- Fixed issue where AWS same-net CFE deployments failed to update cloud resources when BIG-IP instances use 3 network interfaces and the CFE config uses static address definitions. Fixes GitHub Issue #119.
- Fixed issue where not all Azure route tables were updated when CFE received a paginated response from Azure.
- Fixed issue where f5_cloud_failover_nic_map was incorrectly required when using static route definitions in Azure. Fixes GitHub Issue #124.
- Fixed issue where Azure route tables were not updated if the route table contained routes using service tag prefixes.
- Fixed issue where requests to the /inspect endpoint failed if the failoverRoutes block was removed from the CFE configuration. Fixes GitHub Issue #123.
- Fixed issue where performing a dry run in Google Cloud caused CFE to incorrectly update cloud resources.
- Updated resource tag normalization to remove leading and trailing whitespace when comparing tag values.
Documentation:
- Updated troubleshooting section with documentation on identifying and remediating common issues.
- Added Azure control plane migration guidance.
- Updated OpenAPI specification to include static address and route definition examples.
- Updated required AWS role permissions to include replace route permission.
- Added maintenance announcement.
v1.14.0
Features added:
- Improved performance of Azure failover provider and verified functionality in the Azure Fast Path control plane.
Documentation:
- Updated documentation. See the documentation revision history for more information.
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.