Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2023-12-12 15:08:00 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2023-12-12 15:08:00 +0300
commit7045d3816aa7bab6619e9d841f45d5cb8d454f23 (patch)
treece43907d55b157728d1e920536418f41e661633f /doc/user/workspace
parent2d560e614a2d5feea84288c2d1f50b40d796f97a (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/workspace')
-rw-r--r--doc/user/workspace/gitlab_agent_configuration.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/workspace/gitlab_agent_configuration.md b/doc/user/workspace/gitlab_agent_configuration.md
index 856b39814fa..0e35c72c5ef 100644
--- a/doc/user/workspace/gitlab_agent_configuration.md
+++ b/doc/user/workspace/gitlab_agent_configuration.md
@@ -11,12 +11,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136744) in GitLab 16.7. Feature flag `remote_development_feature_flag` removed.
When you [set up a workspace](configuration.md#set-up-a-workspace),
-you must configure remote development for the GitLab agent.
+you must configure the GitLab agent for remote development.
The remote development settings are available in the agent
configuration file under `remote_development`.
You can use any agent defined under the root group of your project,
-provided that remote development is properly configured for that agent.
+provided that the agent is properly configured for remote development.
## Remote development settings
@@ -116,7 +116,7 @@ Use this setting to define a list of IP CIDR ranges to allow as egress destinati
Define egress rules when:
- The GitLab instance is on a private IP range.
-- Workspace users must access a cloud resource on a private IP range.
+- The workspace must access a cloud resource on a private IP range.
Each element of the list defines an `allow` attribute with an optional `except` attribute.
`allow` defines an IP range to allow traffic from.