This commit adds settings for the `storage_options` setting used to
configure AWS server side encryption. Note that only SSE-KMS
(https://docs.aws.amazon.com/kms/latest/developerguide/services-s3.html#sse)
is supported; SSE-C is not.

Related merge requests:

1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38240
2. https://gitlab.com/gitlab-org/gitlab-workhorse/-/merge_requests/537

Cron job introduced in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38086

This also moves the worker pool size setting to an ENV variable
since that was changed in gitlab-rails

This adds support for the gitlab.yml changes in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/34460. This allows
GitLab to use the Workhorse S3 client with a single credential, enabling
proper MD5 checksums and multipart uploads, and paves the way for
user-specified keys for encrypted buckets.

These changes require
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35480 to work.

Ian Baum authored 4 years ago and DJ Mountney committed 4 years ago

runit_service[sidekiq]

It looks like LWRP resources aren't added to the list at compile time,
so there isn't any runit_service[sidekiq] when notifications are being
setup

Ian Baum authored 4 years ago and DJ Mountney committed 4 years ago

* Curently on 14, which was set to end of life at on April 30, 2020.
* Adds chef-bin gem
* Automatically accept the chef license EULA
* Update chef libraries in Gemfile to newer versions
* Update trigger jobs to use ruby 2.6 image

As discussed in
https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4324, we
can set the default attribute for `gitlab_workhorse['auth_socket']` to
`nil` as the empty string value so we can use
`node['gitlab']['gitlab-workhorse']['auth_socket']` in the template
instead of `Gitlab['gitlab_workhorse']['auth_socket']`.

To support continuous profiling in gitlab-pages (https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/334) we need to supply an environment variable (GITLAB_CONTINUOUS_PROFILING).  Before this MR, gitlab-pages had one env var hard-coded into the sv run file.  This MR converts to using chpst's -e option as we do for many of our other services, and permits the configuring of additional env vars from gitlab.rb (as we do for e.g. gitaly and praefect).

* Include `text/html` missing from gzip_types.
* Use the same nginx settings for nginx.conf and gitlab-http.conf.
* Include gzip_ratio in the nginx log format.

https://gitlab.com/gitlab-org/gitlab-foss/-/issues/33719



Signed-off-by: Ben Kochie <bjk@gitlab.com>

Balasankar C authored 4 years ago and DJ Mountney committed 4 years ago

Signed-off-by: Balasankar "Balu" C <balasankarc@autistici.org>

This is the next step in having a single way of running Sidekiq: the
sidekiq config now delegates to sidekiq-cluster by default.

It also updates the shutdown timeout and the max threads to the
defaults for sidekiq-cluster and sidekiq

This also adds support for configuring `sidekiq['shutdown_timeout']`.

Balasankar C authored 4 years ago and DJ Mountney committed 4 years ago

Signed-off-by: Balasankar "Balu" C <balasankarc@autistici.org>

DJ Mountney authored 4 years ago and Balasankar C committed 4 years ago

gitlab-monitor
The switch the monitoring components syntax
The auth-server config item for gitlab-pages

Signed-off-by: Balasankar "Balu" C <balasankarc@autistici.org>

Jan Provaznik authored 4 years ago and Balasankar C committed 4 years ago

When enabled it allows to fetch incoming service desk emails
from a dedicated email address.

Diego Louzán authored 4 years ago and DJ Mountney committed 4 years ago

Related https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29352

Defaults to the same default Redis instance but also allows specifying
a separate Redis instance

Enable git to write a commit graph on git fetch.
This should helps the server to write a CommitGraph during mirror
clone/fetch activities, consistent with current `core` and `gc`
commit-graph configs set within Gitaly.

Git-commit-graph enable faster connectivity check which
makes faster git merge-base, git push -f, and git log --graph.

Reference: https://git-scm.com/docs/git-config#Documentation/git-config.txt-corecommitGraph

Added pack.useSparse as default config in order to help performance of
git-pack-objects
References: see https://git-scm.com/docs/git-pack-objects#Documentation/git-pack-objects.txt---sparse

We're moving to running Sidekiq cluster as a default in the
future. This allows administrators to opt-in to the sidekiq cluster
behaviour already.

This behaviour will copy the configuration of sidekiq to
sidekiq-cluster. So it will respect concurrency and logging settings.

When enabling `cluster` for Sidekiq, this will spin up a single
Sidekiq-cluster and Sidekiq process. Sidekiq-cluster will be
configured with the queue groups set to [`*`]. Which will spin up a
single Sidekiq process picking up all queues.

Gerard Hickey authored 4 years ago and Balasankar C committed 4 years ago

If gitlab_rails['db_statement_timeout'] is set by the user, then it
will pick up its value from postgresql['statement_timeout'].

* Use 4 threads per production recommended value.
* Use 1 worker per CPU per production recommended value.

Fixes: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/3896



Signed-off-by: Ben Kochie <bjk@gitlab.com>