Merge branch 'docs-repo-merge-27-project-i-ee' into 'master'

Docs: (EE Port) Merge misc EE doc/user/project/i* dirs to CE

See merge request gitlab-org/gitlab-ee!12094

doc/user/project/import/gemnasium.md

@@ -9,9 +9,9 @@ Gemnasium has been [acquired by GitLab](https://about.gitlab.com/press/releases/
 in January 2018. Since May 15, 2018, the services provided by Gemnasium are no longer available.
 The team behind Gemnasium has joined GitLab as the new Security Products team
 and is working on a wider range of tools than just Dependency Scanning:
-[SAST](../merge_requests/sast.md),
-[DAST](../merge_requests/dast.md),
-[Container Scanning](../merge_requests/container_scanning.md) and more.
+[SAST](https://docs.gitlab.com/ee/user/application_security/sast/index.html),
+[DAST](https://docs.gitlab.com/ee/user/application_security/dast/index.html),
+[Container Scanning](https://docs.gitlab.com/ee/user/application_security/container_scanning/index.html) and more.
 If you want to continue monitoring your dependencies, see the
 [Migrating to GitLab](#migrating-to-gitlab) section below.
 
@@ -45,7 +45,7 @@ Security features are free for public (open-source) projects hosted on GitLab.co
 You're almost set! If you're already using
 [Auto DevOps](../../../topics/autodevops/), you are already covered.
 Otherwise, you must configure your `.gitlab-ci.yml` according to the
-[dependency scanning page](../merge_requests/dependency_scanning.md).
+[dependency scanning page](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/index.html).
 
 ### If your project is hosted on GitHub (https://github.com / GitHub Enterprise)
 
@@ -81,7 +81,7 @@ back to both GitLab and GitHub when completed.
 
 1. To set up the dependency scanning job, corresponding to what Gemnasium was
    doing, you must create a `.gitlab-ci.yml` file, or update it according to
-   the [dependency scanning docs](../merge_requests/dependency_scanning.md).
+   the [dependency scanning docs](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/index.html).
    The mirroring is pull-only by default, so you may create or update the file on
    GitHub:
 

doc/user/project/import/index.md

@@ -19,7 +19,7 @@ In addition to the specific migration documentation above, you can import any
 Git repository via HTTP from the New Project page. Be aware that if the
 repository is too large the import can timeout.
 
-There is also the option of [connecting your external repository to get CI/CD benefits](../ci_cd_for_external_repo.md).
+There is also the option of [connecting your external repository to get CI/CD benefits](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/index.html). **[PREMIUM]**
 
 ## Migrating from self-hosted GitLab to GitLab.com
 

doc/user/project/insights/index.md

@@ -14,7 +14,7 @@ requests to be merged and much more.
 ![Insights example stacked bar chart](img/project_insights.png)
 
 NOTE: **Note:**
-This feature is [also available at the group level](../../group/insights/index.md).
+This feature is [also available at the group level](https://docs.gitlab.com/ee/user/group/insights/index.html).
 
 ## Configure your Insights
 
@@ -26,7 +26,7 @@ for details about the content of this file.
 
 NOTE: **Note:**
 Once the configuration file is created, you can also
-[use it for your project's group](../../group/insights/index.md#configure-your-insights).
+[use it for your project's group](https://docs.gitlab.com/ee/user/group/insights/index.html#configure-your-insights).
 
 NOTE: **Note:**
 If the project doesn't have any configuration file, it'll try to use

doc/user/project/integrations/project_services.md

@@ -34,12 +34,12 @@ Click on the service links to see further configuration instructions and details
 | [Emails on push](emails_on_push.md) | Email the commits and diff of each push to a list of recipients |
 | External Wiki | Replaces the link to the internal wiki with a link to an external wiki |
 | Flowdock | Flowdock is a collaboration web app for technical teams |
-| [GitHub](github.md) | Sends pipeline notifications to GitHub |
+| [GitHub](github.md) **[PREMIUM]** | Sends pipeline notifications to GitHub |
 | [Hangouts Chat](hangouts_chat.md) | Receive events notifications in Google Hangouts Chat |
 | [HipChat](hipchat.md) | Private group chat and IM |
 | [Irker (IRC gateway)](irker.md) | Send IRC messages, on update, to a list of recipients through an Irker gateway |
 | [JIRA](jira.md) | JIRA issue tracker |
-| [Jenkins](../../../integration/jenkins.md) | An extendable open source continuous integration server |
+| [Jenkins](https://docs.gitlab.com/ee/integration/jenkins.html) **[STARTER]** | An extendable open source continuous integration server |
 | JetBrains TeamCity CI | A continuous integration and build server |
 | [Mattermost slash commands](mattermost_slash_commands.md) | Mattermost chat and ChatOps slash commands |
 | [Mattermost Notifications](mattermost.md) | Receive event notifications in Mattermost |

doc/user/project/integrations/prometheus_library/kubernetes.md

@@ -36,11 +36,11 @@ In order to isolate and only display relevant CPU and Memory metrics for a given
 
 Instead, the [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) or [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) name should begin with [CI_ENVIRONMENT_SLUG](../../../../ci/variables/README.md#predefined-environment-variables). It can be followed by a `-` and additional content if desired. For example, a deployment name of `review-homepage-5620p5` would match the `review/homepage` environment.
 
-## Displaying Canary metrics
+## Displaying Canary metrics **[PREMIUM]**
 
 > Introduced in [GitLab 10.2](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15201).
 
-GitLab also gathers Kubernetes metrics for [canary deployments](../../canary_deployments.md), allowing easy comparison between the current deployed version and the canary.
+GitLab also gathers Kubernetes metrics for [canary deployments](https://docs.gitlab.com/ee/user/project/canary_deployments.html), allowing easy comparison between the current deployed version and the canary.
 
 These metrics expect the [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) or [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) name to begin with `$CI_ENVIRONMENT_SLUG-canary`, to isolate the canary metrics.