Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
parent
81e6c76671
commit
3cdb539841
5 changed files with 12 additions and 13 deletions
|
@ -276,6 +276,8 @@ PostgreSQL instances. Otherwise you should change the configuration parameter
|
|||
|
||||
### Praefect
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitaly/-/issues/2634) in GitLab 13.4, Praefect nodes can no longer be designated as `primary`.
|
||||
|
||||
NOTE: **Note:**
|
||||
If there are multiple Praefect nodes, complete these steps for **each** node.
|
||||
|
||||
|
@ -392,11 +394,6 @@ application server, or a Gitaly node.
|
|||
More Gitaly nodes can be added to the cluster to increase the number of
|
||||
replicas. More clusters can also be added for very large GitLab instances.
|
||||
|
||||
NOTE: **Note:**
|
||||
The `gitaly-1` node is currently denoted the primary. This
|
||||
can be used to manually fail from one node to another. This will be removed
|
||||
in the [future](https://gitlab.com/gitlab-org/gitaly/-/issues/2634).
|
||||
|
||||
```ruby
|
||||
# Name of storage hash must match storage name in git_data_dirs on GitLab
|
||||
# server ('praefect') and in git_data_dirs on Gitaly nodes ('gitaly-1')
|
||||
|
@ -405,7 +402,6 @@ application server, or a Gitaly node.
|
|||
'gitaly-1' => {
|
||||
'address' => 'tcp://GITALY_HOST:8075',
|
||||
'token' => 'PRAEFECT_INTERNAL_TOKEN',
|
||||
'primary' => true
|
||||
},
|
||||
'gitaly-2' => {
|
||||
'address' => 'tcp://GITALY_HOST:8075',
|
||||
|
@ -1044,11 +1040,6 @@ current primary node is found to be unhealthy.
|
|||
will cause Praefect nodes to elect a new primary, monitor its health,
|
||||
and elect a new primary if the current one has not been reachable in
|
||||
10 seconds by a majority of the Praefect nodes.
|
||||
- **Manual:** Automatic failover is disabled. The primary node can be
|
||||
reconfigured in `/etc/gitlab/gitlab.rb` on the Praefect node. Modify the
|
||||
`praefect['virtual_storages']` field by moving the `primary = true` to promote
|
||||
a different Gitaly node to primary. In the steps above, `gitaly-1` was set to
|
||||
the primary. Requires `praefect['failover_enabled'] = false` in the configuration.
|
||||
- **Memory:** Enabled by setting `praefect['failover_election_strategy'] = 'local'`
|
||||
in `/etc/gitlab/gitlab.rb` on the Praefect node. If a sufficient number of health
|
||||
checks fail for the current primary backend Gitaly node, and new primary will
|
||||
|
|
|
@ -288,7 +288,7 @@ to learn more.
|
|||
|---------|-------------|---------|
|
||||
| `provider` | Provider name | `AzureRM` |
|
||||
| `azure_storage_account_name` | Name of the Azure Blob Storage account used to access the storage | `azuretest` |
|
||||
| `azure_storage_access_key` | Storage account access key used to access the container. This is typically a secret, 512-bit encryption key encoded in base64. | `"czV2OHkvQj9FKEgrTWJRZVRoV21ZcTN0Nnc5eiRDJkYpSkBOY1JmVWpYbjJy\nNHU3eCFBJUQqRy1LYVBkU2dWaw==\n"` |
|
||||
| `azure_storage_access_key` | Storage account access key used to access the container. This is typically a secret, 512-bit encryption key encoded in base64. | `czV2OHkvQj9FKEgrTWJRZVRoV21ZcTN0Nnc5eiRDJkYpSkBOY1JmVWpYbjJy\nNHU3eCFBJUQqRy1LYVBkU2dWaw==\n` |
|
||||
| `azure_storage_domain` | Domain name used to contact the Azure Blob Storage API (optional). Defaults to `blob.core.windows.net`. Set this if you are using Azure China, Azure Germany, Azure US Government, or some other custom Azure domain. | `blob.core.windows.net` |
|
||||
|
||||
##### Azure example (consolidated form)
|
||||
|
|
|
@ -44,6 +44,7 @@ The following API resources are available in the project context:
|
|||
| [Members](members.md) | `/projects/:id/members` (also available for groups) |
|
||||
| [Merge request approvals](merge_request_approvals.md) **(STARTER)** | `/projects/:id/approvals`, `/projects/:id/merge_requests/.../approvals` |
|
||||
| [Merge requests](merge_requests.md) | `/projects/:id/merge_requests` (also available for groups and standalone) |
|
||||
| [Merge trains](merge_trains.md) | `/projects/:id/merge_trains` |
|
||||
| [Notes](notes.md) (comments) | `/projects/:id/issues/.../notes`, `/projects/:id/snippets/.../notes`, `/projects/:id/merge_requests/.../notes` (also available for groups) |
|
||||
| [Notification settings](notification_settings.md) | `/projects/:id/notification_settings` (also available for groups and standalone) |
|
||||
| [Packages](packages.md) | `/projects/:id/packages` |
|
||||
|
|
|
@ -18,7 +18,7 @@ For information on how to install, configure, update, and upgrade your own GitLa
|
|||
|
||||
## Get started
|
||||
|
||||
- Set up GitLab's development environment with [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/README.md)
|
||||
- Set up GitLab's development environment with [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/master/README.md)
|
||||
- [GitLab contributing guide](contributing/index.md)
|
||||
- [Issues workflow](contributing/issue_workflow.md) for more information on:
|
||||
- Issue tracker guidelines.
|
||||
|
|
|
@ -206,6 +206,9 @@ variables:
|
|||
DAST_FULL_SCAN_ENABLED: "true"
|
||||
```
|
||||
|
||||
NOTE: **Note:**
|
||||
If your DAST job exceeds the job timeout and you need to reduce the scan duration, we shared some tips for optimizing DAST scans in a [blog post](https://about.gitlab.com/blog/2020/08/31/how-to-configure-dast-full-scans-for-complex-web-applications/).
|
||||
|
||||
#### Domain validation
|
||||
|
||||
The DAST job can be run anywhere, which means you can accidentally hit live web servers
|
||||
|
@ -801,6 +804,10 @@ variables:
|
|||
Here, DAST is being allocated 3072 MB.
|
||||
Change the number after `-Xmx` to the required memory amount.
|
||||
|
||||
### DAST job exceeding the job timeout
|
||||
|
||||
If your DAST job exceeds the job timeout and you need to reduce the scan duration, we shared some tips for optimizing DAST scans in a [blog post](https://about.gitlab.com/blog/2020/08/31/how-to-configure-dast-full-scans-for-complex-web-applications/).
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
|
|
Loading…
Reference in a new issue