The DevOps Toolkit Catalogue/

...

/

Deploy the Applications

Deploy the Applications

Learn how to deploy applications in the namespaces.

We'll cover the following...

Create the production namespace

Now that we've established we’ll allow the apps in the Argo CD production project to be deployed to the production namespace, we should probably create it.

Shell
kubectl create namespace production

Next, let’s take a look at the manifests that will define our applications. They're located in the helm directory.

ls -1 helm

The output is as follows.

Chart.yaml
templates
Files in the helm directory

View the files

At first glance, this looks like a typical minimalistic Helm chart. Actually, it doesn't look like that. It's a Helm chart. What makes it “special” are the resources defined in the templates.

Javascript (babel-node)
ls -1 helm/templates

The output is as follows.

Shell
devops-paradox.yaml
devops-toolkit.yaml

From the names, we can probably guess that those two files define two applications. Let’s take a look at one of those.

Shell
cat helm/templates/devops-toolkit.yaml

The output is as follows.

YAML
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: devops-toolkit
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
spec:
  project: production
  source:
    path: helm
    repoURL: https://github.com/vfarcic/devops-toolkit.git
    targetRevision: HEAD
    helm:
      values: |
        image:
          tag: latest
        ingress:
          host: devopstoolkitseries.com
      version: v3
  destination:
    namespace: production
    server: https://kubernetes.default.svc
  syncPolicy:
    automated:
      selfHeal: true
      prune: true

Note: We'll get hands-on experience with the concepts and commands discussed in this lesson in the project "Hands-on: Deploying Applications Using GitOps Principles" right after this chapter.

The definition is accomplishing a similar objective as the argocd app create command we ...