Release Load Balancer Operator v1.8.0

Features:

• Support Kubernetes [1.23,1.25], Load Balancer and Ingress Service(a.k.a AKO) 1.9.2, NSX Advanced LoadBalancer [21.1.5,22.1.3].

Enhancements:

• Fixed provision cluster endpoint VIP race condition #139

Known issues:

• ClusterClass-based cluster's cluster name can only contain less than 25 characters.

Image:

projects.registry.vmware.com/tkg/ako-operator:v1.8.0_vmware.1

Release Load Balancer Operator v1.7.0

Features:

• Support Kubernetes [1.22,1.24], Load Balancer and Ingress Service(a.k.a AKO) 1.8.2, NSX Advanced LoadBalancer [21.1.3,22.1.2].
• Support CAPI ClusterClass based cluster and latest tanzu addon manager

Enhancements:

• Remove ako pod resource limit

Known issues:

• ClusterClass based cluster's clustername can only contains less than 25 character.

Image:

projects.registry.vmware.com/tkg/ako-operator:v1.7.0_vmware.3

Release Load Balancer Operator v1.6.1

Enhancements:

• Fix CVEs in load balancer operator image
• Fix load balancer operator webhook invalid validation fail:
  • Fix akodeploymentconfig.spec.controlPlaneNetwork can't be an empty error
  • Fix validation fails when NSX Advanced Load Balancer multiple clouds have the same resource name
  • Fix putting the right avi controller version, avi client didn't re-init with the controller version error

Known Issues:

• When using NSX Advanced Load Balancer as Tanzu Kubernetes cluster control plane endpoint VIP provider, the load balancer operator can't reconcile usable network during management cluster creation.

Release Load Balancer Operator v1.6.0

Features:

• Support Kubernetes [1.21,1.23], Load Balancer and Ingress Service(a.k.a AKO) 1.7.2, NSX Advanced LoadBalancer [20.1.6,21.1.4].
• Support workload clusters' endpoints VIP network separation, details can be found here.

Enhancements:

• Refactor AKODeploymentConfig <-> Workload Cluster mapping
• Add webhook to validate and failed early on invalid AKODeploymentConfig changes.
• Automatically detect and update AVI controller version

Known issues:

• When inputting the right AVI controller version, the load balancer operator failed to re-init AVI client using the right controller version.
• AKODeploymentConfig webhook checks ServiceEngineGroup with the same name in the whole AVI controller scope instead of the specific cloud scope, it can't allow duplicate names controller-wise for now.

pre release version before go mod update

v1.6.0-pre-go-mod-update

Add integration test for the new cluster labelling logics. (#92)

Load Balancer Operator v1.5.0

Release Load Balancer Operator v1.5.0

Features:

• Support Load Balancer and Ingress Service(a.k.a AKO) 1.6.1, Kubernetes 1.22 and cluster API v1beta1.
• Expose all AKO configurations in AKODeploymentConfig, significantly reducing multi-cluster condition AKO configuration complexity.
• Support AKO NodePortLocal feature in multi-cluster conditions (This feature requires cluster's CNI is Antrea).
• VIP network separation feature in alpha stage.

Enhancements:

• Change to watch AKO statefulset's annotation to check NSX ALB resource clean-up progress.
• Improve test coverage by adding more integration and unit test cases.
• Deprecate all AKO manifest yaml
• Deprecate AKO image configurations

Fix:

• Fix configuring NSX ALB usable network issue.
• Fix didn't handle NSX ALB resource deletion timeout issue.

Known issues:

• VIP network separation feature:
  • spec.ControlPlaneNetwork configurations can't be omitted even it is empty.
  • there is a race condition when enabling NSX ALB to provide control plane HA, which may cause cluster control plane endpoint change.