Commit 5d0d2e7b authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'add-cluster-detail-page-vulnerabilities-docs' into 'master'

Add docs for cluster detail page vulnerabilities

See merge request gitlab-org/gitlab!78002
parents 73800448 16cd8077
...@@ -301,7 +301,9 @@ the security vulnerabilities in your groups, projects, and pipelines. ...@@ -301,7 +301,9 @@ the security vulnerabilities in your groups, projects, and pipelines.
## Interacting with the vulnerabilities ## Interacting with the vulnerabilities
After a vulnerability is found, you can [address it](../vulnerabilities/index.md). After you find a vulnerability, you can address it in the [vulnerability report](../vulnerabilities/index.md)
or the [GitLab Agent's](../../clusters/agent/install/index.md#view-vulnerabilities-in-cluster-images)
details section.
## Troubleshooting ## Troubleshooting
......
...@@ -71,6 +71,7 @@ based on [Container Network Policies](../../application_security/policies/index. ...@@ -71,6 +71,7 @@ based on [Container Network Policies](../../application_security/policies/index.
from GitLab CI/CD jobs while keeping the cluster's APIs safe and unexposed from GitLab CI/CD jobs while keeping the cluster's APIs safe and unexposed
to the internet. to the internet.
- [Deploy the GitLab Runner in a Kubernetes cluster](https://docs.gitlab.com/runner/install/kubernetes-agent.html). - [Deploy the GitLab Runner in a Kubernetes cluster](https://docs.gitlab.com/runner/install/kubernetes-agent.html).
- [Scan your Kubernetes cluster for vulnerabilities](../../application_security/cluster_image_scanning/index.md).
See the [Agent roadmap](https://gitlab.com/groups/gitlab-org/-/epics/3329) to track its development. See the [Agent roadmap](https://gitlab.com/groups/gitlab-org/-/epics/3329) to track its development.
......
...@@ -194,6 +194,23 @@ the first time or after more than an hour of inactivity. ...@@ -194,6 +194,23 @@ the first time or after more than an hour of inactivity.
To check what else is planned for the Agent's UI and provide feedback, To check what else is planned for the Agent's UI and provide feedback,
see the [related epic](https://gitlab.com/groups/gitlab-org/-/epics/4739). see the [related epic](https://gitlab.com/groups/gitlab-org/-/epics/4739).
### View vulnerabilities in cluster images **(ULTIMATE)**
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/6346) in GitLab 14.8 [with a flag](../../../../administration/feature_flags.md) named `cluster_vulnerabilities`. Disabled by default.
Users with at least the [Developer role](../../../permissions.md)
can view cluster vulnerabilities. You can access them through the [vulnerability report](../../../application_security/vulnerabilities/index.md)
or in your cluster's image through the following process:
1. Configure [cluster image scanning](../../../application_security/cluster_image_scanning/index.md)
to your build process.
1. Go to your Agent's configuration repository.
1. On the left sidebar, select **Infrastructure > Kubernetes clusters**.
1. Select the **Agent** tab.
1. Select the Agent you want to see the vulnerabilities for.
![Cluster Agent security tab UI](../../img/cluster_agent_security_tab_v14_8.png)
## Create multiple Agents ## Create multiple Agents
You can create and install multiple Agents using the same process You can create and install multiple Agents using the same process
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment