fix(doc): Add why i choose layering

batleforc · Sep 12, 2023 · 9bb8f03 · 9bb8f03
1 parent f8586ce
commit 9bb8f03
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/blog/2023-09-12-Layer.md b/blog/2023-09-12-Layer.md
@@ -13,6 +13,12 @@ Well... i kinda change everything... again.
 
 In a attempt to fix some of the problem i had with my previous setup, i decided to change everything. I'm still using the same tools, but i'm using them differently.
 
+What was the kind of problem if encoutered:
+
+- During some deployment, some helm chart were locking all the deployment process due to a missing secret or other stuff. This was due to the fact that my depency were not well defined and that i was deploying a lot of stuff at the same time.
+- One of the probleme was that Zitadel was needed by a lot of other stuff like Harbor, Sonarqube... well all the app that use the SSO. So if Zitadel was not ready, the deployment of all the other app was failing and then kind of interupted the deployment process.
+- well... let's talk about tekton, the version used was not the latest and during the upgrade everything broke down due to incompatible change. So i decided to upgrade everything to the latest version. During the upgrade the webhook of tekton refused to stop and overloard the cluster. So i had to force delete the webhook and broke the cluster.
+
 ### GitOps
 
 The choice has been made to keep it but to change the deployment order/dependency and process. A layering process has been put in place. The idea is to have a layering of the deployment. Each layer is a set of application that are deployed together. The layer are deployed in order of requirement. The layer are: