Page Comparison

...

• Argo CD at TNAP
  • Recently Andreas and Marc gave a talk:

    • LFN Webinar: Deutsche Telekom Deploys ONAP In O-RAN Town (Timestamp 25:51)

  • Two scenarios:
    • Deploy gitlab runner into one k8s cluster
      • Just for learning and getting a feeling
      • The runner settings in Gitlab 
      • https://gitlab.devops.telekom.de/groups/tnap/-/settings/ci_cd
      • similar to https://gitlab.devops.telekom.de/tnap/development/argo-management/-/tree/main/tnap-integration/tnap/gitlab-runner-k8s
      • install the runner in a different cluster like tesla-dev
        • start with version 0.33.1 update it later to 0.34.0

        • add it to all kustomization.yaml's

          Code Block
          language yml theme DJango title gitlab-runner-k8s.yaml
          --- apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: gitlab-runner namespace: argocd annotations: argocd.argoproj.io/sync-wave: "0" spec: project: argo-management syncPolicy: automated: prune: false selfHeal: true destination: namespace: tnap server: https://kubernetes.default.svc source: repoURL: https://charts.gitlab.io chart: gitlab-runner targetRevision: 0.33.1 helm: values: | imagePullSecrets: - name: tnap-docker-registry-key imagePullPolicy: Always gitlabUrl: "https://gitlab.devops.telekom.de/" runnerRegistrationToken: "dnCTzaRs6EK-by1AqQxu" runners: tags: "tnaplab_k8s_test_oom_test_demostration" name: "tnaplab_k8s_test_oom_test_demostration"

          
          

        • 
          

          Code Block
          language yml theme DJango title kustomization.yaml
          --- kind: Kustomization apiVersion: kustomize.config.k8s.io/v1beta1 resources: - gitlab-runner-k8s.yaml

          
          

        • 
          

          Code Block
          language yml theme DJango title kustomization.yaml
          --- kind: Kustomization apiVersion: kustomize.config.k8s.io/v1beta1 resources: - ... - ... - gitlab-runner-k8s/

          
          

        • now update it to version 0.34.0
    • Update an existing ONAP component
      • oom from onap
        • https://gerrit.onap.org/r/admin/repos/oom
        • https://gerrit.onap.org/r/gitweb?p=oom.git;a=tree;h=refs/heads/istanbul;hb=refs/heads/istanbul
      • In our case, we split the oom repo into several repos. One helm chart repo for each onap component.
        
      • and yesterday we had the increase the internal version number of dmaap (from 8.0.1 to 8.0.1-1) 

      • 

        Code Block
        language yml theme DJango
        @@ -16,4 +16,4 @@ apiVersion: v1 description: ONAP DMaaP components name: dmaap - version: 8.0.1 + version: 8.0.1-1

        
        

      • and we put it into our artifactory (JFrog), similar to nexus

      • 

        
        

      • Now we need to update it in our argo-management repo to the version 8.0.1-1 as well

      • and watch it in Argo CD, how it is being updated
      • 
  • Outlook were we like to get better:
    • https://static.sched.com/hosted_files/kccncna20/39/GitOpsIsMoreThanYouThink.pdf
    • Remark:
      • Show slide 21 to 24 (pull request automatisation) → hint https://github.com/argoproj-labs/argocd-image-updater
      • Show slide 26 (Environment Customizations) - use a base config with kustomize
    • Notifications: https://argocd-notifications.readthedocs.io/en/stable/services/slack/
  • Summary of Argo:

    • Manage More Clusters with Less Hassle, with Argo CD Application Sets - Jonathan West & Kshama Jain (4:05)

    • Good to know: The Argo Architecture https://argo-cd.readthedocs.io/en/stable/operator-manual/architecture/
  • More from Argo / other projects:
    • All from: The Argo Ecosystem: Tailoring Your Installation Through Comm... Jesse Suen & Alexander Matyushentsev
      
      • Argo at a glance (1:15)
      • Argo Design philosophy (4:09)
      • Argo makes heavy use of Annotations (4:27)
      • Argo benefits of individuals projects (5:09)
  • Offtopic/Backup:

    • argo-management repo has linters in place

      Code Block
      language bash theme DJango
      ➜ argo-management git:(main) pre-commit run --all-files Check Yaml...............................................................Passed Fix End of Files.........................................................Passed Trim Trailing Whitespace.................................................Passed yamllint.................................................................Passed k8svalidate..............................................................Passed

      
      

...