In GitLab 13.0,
sidekiq-cluster was enabled by default and the
sidekiq-cluster under the hood. However, users could control this
sidekiq['cluster'] setting to run Sidekiq directly instead.
Users could also run
sidekiq-cluster separately using the various
sidekiq_cluster[*] settings available in
gitlab.rb. However these features
were deprecated and are now being removed.
Starting with GitLab 14.0,
sidekiq-cluster becomes the only way to run Sidekiq
omnibus-gitlab installations. As part of this process, support for the
following settings in
gitlab.rb is being removed:
sidekiq['cluster']setting. Sidekiq can only be run using
sidekiq_cluster[*]settings. They should be set via respective
sidekiq['concurrency']setting. The limits should be controlled using the two settings
In GitLab 13.0, Puma became the default web server for GitLab, but users were
still able to continue using Unicorn if needed. Starting with GitLab 14.0,
Unicorn is no longer supported as a webserver for GitLab and is no longer
shipped with the
omnibus-gitlab packages. Users must migrate to Puma following
to upgrade to GitLab 14.0.
The Consul version has been updated from
1.9.6 for Geo and multi-node PostgreSQL installs. Its important
that Consul nodes be upgraded and restarted one at a time.
See our Consul upgrade instructions.
Starting with GitLab 14.0, GitLab automatically generates a password for initial
administrator user (
root) and stores this value to
/etc/gitlab/initial_root_password. For details, see the
documentation on initial login.
The binaries for PostgreSQL 11 and repmgr have been removed.
Prior to upgrading, administrators using Omnibus GitLab must: