Skip to content
Snippets Groups Projects

Increase entity limits for agent ci_access and user_access to 500

Merged Viktor Nagy (GitLab) requested to merge nagyv-agent-limits into master
All threads resolved!
2 files
+ 4
4
Compare changes
  • Side-by-side
  • Inline
Files
2
@@ -80,7 +80,7 @@ To authorize the agent to access the GitLab project where you keep Kubernetes ma
- Authorized projects must have the same root group or user namespace as the agent's configuration project.
- You can install additional agents into the same cluster to accommodate additional hierarchies.
- You can authorize up to 100 projects.
- You can authorize up to 500 projects.
All CI/CD jobs now include a `kubeconfig` file with contexts for every shared agent connection.
The `kubeconfig` path is available in the environment variable `$KUBECONFIG`.
@@ -106,7 +106,7 @@ To authorize the agent to access all of the GitLab projects in a group or subgro
- Authorized groups must have the same root group as the agent's configuration project.
- You can install additional agents into the same cluster to accommodate additional hierarchies.
- All of the subgroups of an authorized group also have access to the same agent (without being specified individually).
- You can authorize up to 100 groups.
- You can authorize up to 500 groups.
All the projects that belong to the group and its subgroups are now authorized to access the agent.
All CI/CD jobs now include a `kubeconfig` file with contexts for every shared agent connection.
Loading