badhouseplants/badhouseplants-net-old
Archived
4
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Activity

chore: Do some cleanup in the static directory

Browse Source
This commit is contained in:
Nikolai Rodionov
2023-04-17 17:23:30 +02:00
parent 542f4cc562
commit 1d43c273ee
58 changed files with 47 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/dont-use-argocd-for-infrastructure/index.md
View File

@ -21,11 +21,11 @@ Let's assume you are a team that is providing something as a service to other te
> It's very common to use separated clusters for different teams, customers, applications, etc. Let's say you have 3 clusters
![3 clusters and you](/dont-use-argocd-for-infrastructure/3-clusters.png)
![3 clusters and you](/posts/dont-use-argocd-for-infrastructure/3-clusters.png)
Setups may be different, you can use different clusters for different products, environments, teams, or you can have your own opinion on how to split workload between clusters. But these (in our case) 3 clusters are used directly by other teams. Also, you may want to have a cluster for providing services, let's assume, your company decided to use [Gitea](https://gitea.io/en-us/) as a `git` provider, and you deployed it to Kubernetes. *It may be a very controversial example, but I'm not talking about what should run in K8s and what shouldn't, so if you can think of any other thing, that is supposed to be used across the whole company (GitLab Runners, Bitwarden, ElasticSearch, etc...)*. So it's already 4 clusters. Let's call the fourth cluster a `DevOps Cluster`
![3 Clusters and gitea](/dont-use-argocd-for-infrastructure/3-clusters-and-gitea.png)
![3 Clusters and gitea](/posts/dont-use-argocd-for-infrastructure/3-clusters-and-gitea.png)
I assume you need to have some common stuff deployed to each cluster, let's think of (Prometheus, Grafana and Loki).