Until the final removal in 17.0, features built on this integration will continue to work, if you enable the feature flag. In GitLab 17.0 we will remove both the feature and its related code. However, the feature flag will be disabled by default, so this change is a breaking change. The certificate-based integration with Kubernetes will be deprecated and removed.Īs a self-managed customer, we are introducing the feature flag certificate_based_clusters in GitLab 15.0 so you can keep your certificate-based integration enabled. You need to take care with the migration to avoid losing jobs entirely. You can follow the migration guide from queue selectors to routing rules. While the above approach is recommended for most instances, Sidekiq can also be run using routing rules which is also being used on. Note that Sidekiq can effectively run as many processes as the number of CPUs in the machine. This approach is also recommended in our Reference Architecture. For example, if Sidekiq is currently running with 4 processes (denoted by 4 elements in sidekiq in /etc/gitlab/gitlab.rb) with queue selector ( sidekiq = true), you can change Sidekiq to listen to all queues in all 4 processes,for example sidekiq = * 4. You can migrate away from queue selectors to listening to all queues in all processes. Running Sidekiq with a queue selector (having multiple processes listening to a set of queues) and negate settings is deprecated and will be fully removed in 17.0. To discuss this change or learn more, see the deprecation issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |