#Release Notes

#Compatibility and support matrix

The following table shows the compatibility and support matrix between the Alauda Build of Gitlab operator and ACP versions.

#v17.11.4

#Features and Enhancements

#Alauda Build of Gitlab

Fixed vulnerabilities by applying critical security patches to both the operator and gitlab components.

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.

#v17.11.3

#Features and Enhancements

#Alauda Build of Gitlab

Fixed vulnerabilities by applying critical security patches to both the operator and gitlab components.

#Fixed Issues

• Before this update, when deploying GitLab in high availability mode, the praefect component did not have default resource requests and limits configured, which could lead to resource contention or unpredictable scheduling behavior. With this update, the praefect component includes default resource settings with requests of 500m CPU and 500Mi memory, and limits of 2 CPU and 2Gi memory.
• Before this update, when users created instances of different tools (for example, GitLab and Harbor) with the same name, the later instance could be created but failed during deployment. With this update, the operator blocks the creation of duplicate names by returning an error, prompting users to change the release name.

#Known Issues

No issues in this release.

#v17.11.2

#Features and Enhancements

#Alauda Build of Gitlab

The Alauda Build of Gitlab operator now integrates the community edition of Gitlab version 17.11.7. By this update, this operator enables users to leverage the latest features and improvements from the Gitlab community, supporting efficient software development workflows.

To know more about Gitlab v17.11 features, please visit Gitlab v17.11 Release Blog.

#AML Template

Before this update, deploying a Gitlab instance with LFS support required first using a template to deploy Gitlab and then manually configuring the LFS feature according to the product documentation, which was complex and error-prone. With this update, you can directly use the AML Template to deploy a Gitlab instance with built-in LFS support, simplifying the process and reducing the risk of configuration errors.

#Fixed Issues

• Before this update, the operator continuously reconciled GitLab instances because of the HPA resource, which resulted in high CPU usage. With this update, the operator reconciles GitLab instances normally, reducing CPU consumption.

#Known Issues

No issues in this release.

#v17.11.1

#Features and Enhancements

#Alauda Build of Gitlab

The Alauda Build of Gitlab operator now integrates the community edition of Gitlab version 17.11.4. By this update, this operator enables users to leverage the latest features and improvements from the Gitlab community, supporting efficient software development workflows.

To know more about Gitlab v17.11 features, please visit Gitlab v17.11 Release Blog.

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.