Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
f385f1c4
Commit
f385f1c4
authored
Jun 08, 2021
by
Mikhail Mazurskiy
Committed by
Marcia Ramos
Jun 08, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document using distinct configuration for concurrent project sync
parent
83ecd3c1
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
51 additions
and
1 deletion
+51
-1
doc/user/clusters/agent/index.md
doc/user/clusters/agent/index.md
+1
-1
doc/user/clusters/agent/repository.md
doc/user/clusters/agent/repository.md
+50
-0
No files found.
doc/user/clusters/agent/index.md
View file @
f385f1c4
...
...
@@ -462,7 +462,7 @@ The setup process follows the same steps as [GitOps](#get-started-with-gitops-an
with the following differences:
- When you define a configuration repository, you must do so with [Cilium settings](#define-a-configuration-repository-with-cilium-settings).
- You do not need to
create a `manifest.yaml`
.
- You do not need to
specify the `gitops` configuration section
.
### Define a configuration repository with Cilium settings
...
...
doc/user/clusters/agent/repository.md
View file @
f385f1c4
...
...
@@ -95,6 +95,56 @@ gitops:
-
glob
:
'
/**/*.{yaml,yml,json}'
```
### Using multiple manifest projects
Storing Kubernetes manifests in more than one repository can be handy, for example:
-
You may store manifests for different applications in separate repositories.
-
Different teams can work on manifests of independent projects in separate repositories.
To use multiple repositories as the source of Kubernetes manifests, specify them in the list of
`manifest_projects`
in your
`config.yaml`
:
```
yaml
gitops
:
manifest_projects
:
-
id
:
group1/project1
-
id
:
group2/project2
```
Note that repositories are synchronized
**concurrently**
and
**independently**
from each other,
which means that, ideally, there should
**not**
be any dependencies shared by these repositories.
Storing a logical group of manifests in a single repository may work better than distributing it across several
repositories.
You cannot use a single repository as a source for multiple concurrent synchronization
operations. If such functionality is needed, you may use multiple agents reading
manifests from the same repository.
Ensure not to specify "overlapping" globs to avoid synchronizing the same files more than once.
This is detected by the GitLab Kubernetes Agent and leads to an error.
INCORRECT - both globs match
`*.yaml`
files in the root directory:
```
yaml
gitops
:
manifest_projects
:
-
id
:
project1
paths
:
-
glob
:
'
/**/*.yaml'
-
glob
:
'
/*.yaml'
```
CORRECT - single globs matches all
`*.yaml`
files recursively:
```
yaml
gitops
:
manifest_projects
:
-
id
:
project1
paths
:
-
glob
:
'
/**/*.yaml'
```
## Surface network security alerts from cluster to GitLab
The GitLab Agent provides an
[
integration with Cilium
](
index.md#kubernetes-network-security-alerts
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment