Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
gitops-getting-started
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
kubernetes
automation
releases
gitops-getting-started
Commits
1487ac56
Commit
1487ac56
authored
5 years ago
by
Ricardo Rocha
Browse files
Options
Downloads
Patches
Plain Diff
Add faq on multi cluster deployments
parent
93256351
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+12
-0
12 additions, 0 deletions
README.md
with
12 additions
and
0 deletions
README.md
+
12
−
0
View file @
1487ac56
...
@@ -145,3 +145,15 @@ To restrict the deployment in this cluster to a single release, pass the allowed
...
@@ -145,3 +145,15 @@ To restrict the deployment in this cluster to a single release, pass the allowed
helm
install
fluxcd/helm-operator
--namespace
flux
--name
helm-operator
--values
helm-operator-values.yaml
--set
allowNamespace
=
stg
helm
install
fluxcd/helm-operator
--namespace
flux
--name
helm-operator
--values
helm-operator-values.yaml
--set
allowNamespace
=
stg
```
```
#### Can i deploy the application in multiple clusters?
Absolutely. The repository knows nothing about the clusters the application
will be deployed in, which is an advantage as you don't have to set the
credentials anywhere outside the cluster(s).
Deploying multiple times in different clusters will also help you reduce blast
radius, is a good way to perform upgrades by redeploying the full setup and
gradually moving resources to the new instance, and it's one of the
alternatives to achieve high availability.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment