Feat kubernetes support (#4)

* feat: folder structure to support kubernetes resources

* updating README.md

* addressing comments

README.md

@@ -2,32 +2,33 @@
 
 A repository that includes YAML manifests. Manifests can define GCP resources in `config connector` format or the Kubernetes components and resources. Refer to this repo for additionnal information. TODO: add link
 
+- The `/*/configcontroller` folder is where GCP resources are defined using their `config connector` schema.
+- The `/*/kubernetes/<x-fleet-id>/**/<namespace>` folder is where resources that have to be provisionned in a kubernetes `namespace` are defined. The `x-fleet-id` is the GCP project-id where the kubernetes clusters are deployed with character "x" as the environment code because this folder will contain the configuration for all environments.
+
+  The GKE clusters are joined to an [Anthos Fleet](https://cloud.google.com/anthos/fleet-management/docs). This enables Anthos policy controller, Anthos config management and Anthos service mesh(future).
+
 ## csync
 
 The `/csync` contains the configuration for what the ConfigSync operator should be observing. For example, It is within this configuration that you specify the `repo url`, the `folder`, the `branch` and the `tag`.
 
-Contributing:
+### Contributing
 
 - Any modification should be implemented within the `source-customization` folder.
 
 ## tier1
 
 The `/tier1` folder is where the core landing zone resources that enables the underneath structure to work.
 
-Contributing:
+### Contributing
 
 - Any modification should be implemented within the `source-customization` folder.
 
-## Permissions
+### Permissions
 
 A pull request affecting `/*` will include the Security Admin and Platform admin as required reviewers.
 
-## Tags
-
-Tags are generated only when changes are affecting the `/tier1` folder. This functionality is possible because of the `version-tagging` pipeline.
-
-The tags will be created by that pipeline job after commits are merge to the `main` branch.
+## Branch Protection
 
-### **IMPORTANT**
+The main branch of this repository is protected meaning that pushing a new commit to it will be denied. To implement changes, A Pull Request has to be completed.
 
-We recommend using those tags in the `setters-version.yaml` under the `/csync/source-customization` folder to define what has to be observed by the configsync operator.
+Every other branches configured to be observed by ConfigSync will also have a branch protection rule defined.

csync/tier1/configcontroller/csync-tier1-ctlr.md

@@ -0,0 +1,3 @@
+# Bookmark
+
+A simple bookmark to help you identify the parent folders

csync/source-base/root-sync-git/Kptfile → csync/tier1/configcontroller/source-base/root-sync-git/Kptfile

@@ -7,7 +7,7 @@ metadata:
 info:
   description: |
     Landing Zone v2 package
-    A package to setup a git repository root sync
+    A package to setup a t1 git repository root sync
 pipeline:
   mutators:
     - image: gcr.io/kpt-fn/apply-setters:v0.2

csync/source-base/root-sync-git/root-sync-git.yaml → csync/tier1/configcontroller/source-base/root-sync-git/root-sync-git.yaml

@@ -2,14 +2,14 @@
 apiVersion: configsync.gke.io/v1beta1
 kind: RootSync
 metadata:
-  name: id-folder # kpt-set: ${id}-${folder}
+  name: id-t1 # kpt-set: ${id}-t1
   namespace: config-management-system
 spec:
   sourceFormat: unstructured
   git:
     repo: https://[email protected]/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME # kpt-set: ${repo-url}
     branch: main # kpt-set: ${repo-branch}
-    dir: deploy/env # kpt-set: ${repo-dir}
+    dir: tier1/configcontroller/deploy/<env> # kpt-set: ${repo-dir}
     revision: HEAD # kpt-set: ${version}
     auth: token
     secretRef:

csync/source-base/root-sync-git/setters.yaml → csync/tier1/configcontroller/source-base/root-sync-git/setters.yaml

@@ -6,17 +6,11 @@ metadata:
     config.kubernetes.io/local-config: 'true'
 data:
   # Used for naming of the root-sync
-  ## id :
-  ### tier1: 'experimentation' or 'env'
-	### tier2: [client-name]
-	### tier34: [project-id] (we replace environment code with “x”)
-  id: id1
-  ## Folder: 'csync' or 'tier1' or 'tier2'
-  ## 'tier3' or 'tier4' are used only with RepoSync
-  folder: tier1
+  ## id is 'experimentation' or 'env'
+  id: id
 
   # Git repo values
   repo-url: https://[email protected]/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
   # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
   repo-branch: main
-  repo-dir: tier1/deploy/env
+  repo-dir: tier1/configcontroller/deploy/<env>

csync/source-customization/dev/root-sync-git/setters.yaml → csync/tier1/configcontroller/source-customization/dev/root-sync-git/setters.yaml

@@ -6,17 +6,11 @@ metadata:
     config.kubernetes.io/local-config: 'true'
 data:
   # Used for naming of the root-sync
-  ## id :
-  ### tier1: 'experimentation' or 'env'
-	### tier2: [client-name]
-	### tier34: [project-id] (we replace environment code with “x”)
+  ## id is 'experimentation' or 'env'
   id: env
-  ## Folder: 'csync' or 'tier1' or 'tier2'
-  ## 'tier3' or 'tier4' are used only with RepoSync
-  folder: tier1
 
   # Git repo values
   repo-url: https://[email protected]/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
   # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
   repo-branch: main
-  repo-dir: tier1/deploy/dev
+  repo-dir: tier1/configcontroller/deploy/dev

csync/source-customization/experimentation/root-sync-git/setters.yaml → csync/tier1/configcontroller/source-customization/experimentation/root-sync-git/setters.yaml

@@ -6,17 +6,11 @@ metadata:
     config.kubernetes.io/local-config: 'true'
 data:
   # Used for naming of the root-sync
-  ## id :
-  ### tier1: 'experimentation' or 'env'
-	### tier2: [client-name]
-	### tier34: [project-id] (we replace environment code with “x”)
+  ## id is 'experimentation' or 'env'
   id: experimentation
-  ## Folder: 'csync' or 'tier1' or 'tier2'
-  ## 'tier3' or 'tier4' are used only with RepoSync
-  folder: tier1
 
   # Git repo values
   repo-url: https://[email protected]/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
   # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
   repo-branch: main
-  repo-dir: tier1/deploy/experimentation
+  repo-dir: tier1/configcontroller/deploy/experimentation

csync/source-customization/prod/root-sync-git/setters.yaml → csync/tier1/configcontroller/source-customization/preprod/root-sync-git/setters.yaml

@@ -6,17 +6,11 @@ metadata:
     config.kubernetes.io/local-config: 'true'
 data:
   # Used for naming of the root-sync
-  ## id :
-  ### tier1: 'experimentation' or 'env'
-	### tier2: [client-name]
-	### tier34: [project-id] (we replace environment code with “x”)
+  ## id is 'experimentation' or 'env'
   id: env
-  ## Folder: 'csync' or 'tier1' or 'tier2'
-  ## 'tier3' or 'tier4' are used only with RepoSync
-  folder: tier1
 
   # Git repo values
   repo-url: https://[email protected]/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
   # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
   repo-branch: main
-  repo-dir: tier1/deploy/prod
+  repo-dir: tier1/configcontroller/deploy/preprod

csync/source-customization/preprod/root-sync-git/setters.yaml → csync/tier1/configcontroller/source-customization/prod/root-sync-git/setters.yaml

@@ -6,17 +6,11 @@ metadata:
     config.kubernetes.io/local-config: 'true'
 data:
   # Used for naming of the root-sync
-  ## id :
-  ### tier1: 'experimentation' or 'env'
-	### tier2: [client-name]
-	### tier34: [project-id] (we replace environment code with “x”)
+  ## id is 'experimentation' or 'env'
   id: env
-  ## Folder: 'csync' or 'tier1' or 'tier2'
-  ## 'tier3' or 'tier4' are used only with RepoSync
-  folder: tier1
 
   # Git repo values
   repo-url: https://[email protected]/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
   # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
   repo-branch: main
-  repo-dir: tier1/deploy/preprod
+  repo-dir: tier1/configcontroller/deploy/prod

tier1/configcontroller/tier1-ctlr.md

@@ -0,0 +1,3 @@
+# Bookmark
+
+A simple bookmark to help you identify the parent folders