Update and rename 2024-06-06-cdks8s-through-argocd.md to 2024-06-06-cdk8s-through-argocd.md

Author: QuadmanSWE

…osts/2024-06-06-cdks8s-through-argocd.md …posts/2024-06-06-cdk8s-through-argocd.mddocs/_posts/2024-06-06-cdks8s-through-argocd.md renamed to docs/_posts/2024-06-06-cdk8s-through-argocd.md docs/_posts/2024-06-06-cdks8s-through-argocd.md renamed to docs/_posts/2024-06-06-cdk8s-through-argocd.md

@@ -1,5 +1,5 @@
 ---
-title: cdks8s through ArgoCD
+title: cdk8s through ArgoCD
 published: true
 excerpt: |
  cdk8s is a tool from AWS to be able to deal with kubernetes manifests in an imperative way which for a lot of people accelerates their investment in learning about and using kubernetes. Though not perhaps inline with the declarative nature of traditional gitops approaches, it is not really that different from jsonnet, helm and/or kustomize which I think simplifies a lot in terms of expressing not only what we want deployed but also how to best manage changes to that state.
@@ -256,4 +256,4 @@ Here is what the running app looks like through ArgoCD.
 
 The act of making sure an application or piece of infrastructure is deployed as desired is the key of gitops, it should not have too strong oppinions on how to express that desired state as long as it can be rendered into clear, straightforward, nonambiguous yaml.
 
-Thus if we are managing a gitops solution we can create a great experience in managing both applications and infrastructure with rich high level tools without sacrificing the reconciliation loop of kubernetes.
+Thus if we are managing a gitops solution we can create a great experience in managing both applications and infrastructure with rich high level tools without sacrificing the reconciliation loop of kubernetes.