Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ee into docs-add-badges-ee

.gitlab/merge_request_templates/Database Changes.md

@@ -45,4 +45,4 @@ When removing columns, tables, indexes or other structures:
 - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
 - [ ] Internationalization required/considered
 - [ ] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
-- [ ] End-to-end tests pass (`package-qa` manual pipeline job)
+- [ ] End-to-end tests pass (`package-and-qa` manual pipeline job)

doc/administration/geo/replication/database.md

@@ -354,12 +354,15 @@ The following guide assumes that:
     gitlab-ctl reconfigure
     ```
 
-1. Restart PostgreSQL for its changes to take effect:
+1. Restart PostgreSQL for the IP change to take effect and Reconfigure again:
 
     ```bash
     gitlab-ctl restart postgresql
+    gitlab-ctl reconfigure
     ```
     
+    This last reconfigure will provision the FDW configuration and enable it.
+
 ### Step 3. Initiate the replication process
 
 Below we provide a script that connects the database on the secondary node to

doc/administration/plugins.md

@@ -33,6 +33,10 @@ Follow the steps below to set up a custom hook:
    For an installation from source the path is usually
    `/home/git/gitlab/plugins/`. For Omnibus installs the path is
    usually `/opt/gitlab/embedded/service/gitlab-rails/plugins`.
+
+    For [highly available] configurations, your hook file should exist on each
+    application server.
+
 1. Inside the `plugins` directory, create a file with a name of your choice,
    without spaces or special characters.
 1. Make the hook file executable and make sure it's owned by the git user.
@@ -78,3 +82,4 @@ Validating plugins from /plugins directory
 
 [system hooks]: ../system_hooks/system_hooks.md
 [webhooks]: ../user/project/integrations/webhooks.md
+[highly available]: ./high_availability/README.md
\ No newline at end of file

doc/install/kubernetes/gitlab_runner_chart.md

@@ -72,6 +72,18 @@ concurrent: 10
 ##
 checkInterval: 30
 
+## For RBAC support:
+rbac:
+  create: false
+
+  ## Run the gitlab-bastion container with the ability to deploy/manage containers of jobs
+  ## cluster-wide or only within namespace
+  clusterWideAccess: false
+
+  ## Use the following Kubernetes Service Account name if RBAC is disabled in this Helm chart (see rbac.create)
+  ##
+  # serviceAccountName: default
+
 ## Configuration for the Pods that that the runner launches for each new job
 ##
 runners:
@@ -116,6 +128,12 @@ runners:
 
 ```
 
+### Enabling RBAC support
+
+If your cluster has RBAC enabled, you can choose to either have the chart create its own sevice account or provide one.
+
+To have the chart create the service account for you, set `rbac.create` to true. 
+
 ### Controlling maximum Runner concurrency
 
 A single GitLab Runner deployed on Kubernetes is able to execute multiple jobs in parallel by automatically starting additional Runner pods. The [`concurrent` setting](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section) controls the maximum number of pods allowed at a single time, and defaults to `10`.

doc/user/project/index.md

@@ -52,6 +52,7 @@ and time spent on
 templates for issue and merge request description fields for your project
 - [Slash commands (quick actions)](quick_actions.md): Textual shortcuts for
 common actions on issues or merge requests
+- [Web IDE](web_ide/index.md)
 
 **GitLab CI/CD:**
 

doc/user/project/web_ide/index.md

 # Web IDE
 
 > [Introduced in](https://gitlab.com/gitlab-org/gitlab-ee/issues/4539) [GitLab Ultimate][ee] 10.4.
-> [Brought to GitLab Core][core](https://gitlab.com/gitlab-org/gitlab-ce/issues/44157) in 10.7.
+> [Brought to GitLab Core](https://gitlab.com/gitlab-org/gitlab-ce/issues/44157) in 10.7.
 
 The Web IDE editor makes it faster and easier to contribute changes to your
 projects by providing an advanced editor with commit staging.
@@ -17,8 +17,8 @@ navigate to **Settings > Preferences**, check **Enable Web IDE** and save.
 
 ## Open the Web IDE
 
-Once enabled, the Web IDE can be opened when viewing a file, from the
-repository file list.
+The Web IDE can be opened when viewing a file, from the repository file list,
+and from merge requests.
 
 ![Open Web IDE](img/open_web_ide.png)
 
@@ -30,4 +30,13 @@ the 'Commit Button'.
 
 ![Commit changes](img/commit_changes.png)
 
+## Comparing changes
+
+Before you commit your changes, you can compare them with the previous commit
+by switching to the review mode or selecting the file from the staged files
+list.
+
+An additional review mode is available when you open a merge request, which
+shows you a preview of the merge request diff if you commit your changes.
+
 [ee]: https://about.gitlab.com/pricing/