josiemundi/refarch-kc-gitops

Event-driven Architecture reference implementation GitOps repository

refarch-kc-gitops

Event Driven Architecture reference implementation GitOps repository, in support of https://ibm-cloud-architecture.github.io/refarch-eda/

Deploying KContainer Reference Implementation using GitOps templates

1. Create a new branch based on the starter-template branch, using the format of <namespace>/<clustername>

   • Example: git checkout starter-template && git checkout -b demo-sandbox/roks-demos.us-east.containers.appdomain.cloud

2. Update the UI microservice's Ingress deployment YAML to contain an appropriate host value.

   • Reference: Red Hat OpenShift on IBM Cloud - Exposing apps that are inside your cluster to the public
   • Example: kcontainer-demo.roks-demos.us-east.containers.appdomain.cloud

3. Commit and push your updated branch to a git repository that will be accessible from your cluster.

4. Create all the necessary pre-requisites in the target cluster:

   1. Ensure ArgoCD is installed and functional. Link
   2. Configure necessary backing components, like Kafka, Event Streams, or Postgresql. Link
   3. Create necessary Kubernetes ConfigMaps and Secrets, which will connect the microservices to the backing components. Link
      • The template YAMLs use the reasonable default names of the necessary ConfigMaps and Secrets, so the YAMLs will not need to be altered if you follow the deployment instructions exactly.
      • You may use different names for the ConfigMaps and Secrets, but you will need to adjust the references in the YAMLs accordingly. This should only be necessary if deploying multiple times to the same namespace.
   4. Configure Service Account, as required by OpenShift or Kubernetes. Link

5. Create an ArgoCD application deployment for each microservice you wish to deploy, using either the ArgoCD CLI, applying application manifest YAMLs through the ArgoCD UI, or apply application manifest YAMLs through the Kubernetes CRDs:

   • ArgoCD CLI:

   argocd app create kcontainer-order-command-ms \
   --repo https://github.com/ibm-cloud-architecture/refarch-kc-gitops.git \
   --revision demo-sandbox/roks-demos.us-east.containers.appdomain.cloud \
   --path kc-ui --directory-recurse --dest-server https://kubernetes.default.svc \
   --dest-namespace demo-sandbox --sync-policy automated --self-heal --auto-prune

   • ArgoCD UI Manifest YAML:

   project: default
   source:
     repoURL: 'https://github.com/ibm-cloud-architecture/refarch-kc-gitops.git'
     path: kc-ui
     targetRevision: demo-sandbox/roks-demos.us-east.containers.appdomain.cloud
     directory:
       recurse: true
       jsonnet: {}
   destination:
     server: 'https://kubernetes.default.svc'
     namespace: demo-sandbox
   syncPolicy:
     automated:
       prune: true
       selfHeal: true

   • ArgoCD CRD YAML:

   apiVersion: argoproj.io/v1alpha1
   metadata:
     name: kc-ui-ms
   spec:
     project: default
     source:
      repoURL: 'https://github.com/ibm-cloud-architecture/refarch-kc-gitops.git'
      path: kc-ui
      targetRevision: demo-sandbox/roks-demos.us-east.containers.appdomain.cloud
      directory:
        recurse: true
        jsonnet: {}
     destination:
      server: 'https://kubernetes.default.svc'
      namespace: demo-sandbox
     syncPolicy:
      automated:
        prune: true
        selfHeal: true

6. You should be able to see ArgoCD applying the YAMLs to the target cluster by watching kubectl get pods.

7. Validate all application Status conditions are both Healthy and Synced before verifying your application deployment in the application UI.

Generating KContainer Reference Implementation GitOps templates

1. Generate all your necessary Kubernetes YAMLs by following the deployment steps documented in https://ibm-cloud-architecture.github.io/refarch-kc/deployments/application-components/, passing in specific values for the desired configuration.
2. Copy the generated YAMLs to the root of your new branch in the repository.
   • Example: <repo_root>/ordercommandms/templates
3. Commit and push your generated YAMLs to this repository on your new branch. Note that the master branch is protected and will not accept pushes, so you will only be able to push to your branch.
4. Continue with Templates Step #4 above.
5. Validate all application Status conditions are both Healthy and Synced before verifying your application deployment in the UI.