archived the channel

Can we render an app that's part of an applicationset locally? Basically I want to see the desired manifest based on the resources on my lappy386 without any regard to what's going on anywhere else not on my lappy.

What factors do you consider when determining which values path you take in the examples shown at https://argo-cd.readthedocs.io/en/stable/user-guide/helm/#values?

Good morning, Is it possible to deploy apps in argocd without creating a root app or using kubectl apply to create applications atleast once? I thought once I add a private repo to my argocd instance it should automatically deploy the manifests in my repository

Hi folks, I'm looking for suggestions on how to inject secret values into my Application manifest. Currently, I'm using the argocd-vault-plugin to fetch secrets from Google Secret Manager.
However, I'm unsure about the best approach for retrieving those values and incorporating them into my application manifest.
I've searched extensively, but I couldn't find any helpful references. Any assistance would be greatly appreciated. Thank you! 🙏🏽

# base/elasticsearch.yaml
---
apiVersion: <http://argoproj.io/v1alpha1|argoproj.io/v1alpha1>
kind: Application
metadata:
  name: elasticsearch
  namespace: argocd
spec:
  project: my-project
  destination:
    name: in-cluster
    namespace: default
  sources:
    - chart: elasticsearch
      repoURL: <https://helm.elastic.co>
      targetRevision: 8.5.1
      helm:
        parameters:
          - name: secret.password
            value: "password"

# overlays/deployment/secrets/secrets.yaml
---
kind: Secret
apiVersion: v1
metadata:
  name: elasticsearch
  annotations:
    <http://avp.kubernetes.io/path|avp.kubernetes.io/path>: projects/1234567890/secrets/elasticsearch
    type: Opaque
data:
  elasticsearch-password: <elasticsearch-secrets | jsonPath {.elasticsearch-password} | base64encode>

How far can you nest the app of apps concept? I’m trying to nest it so I can delegate ownership (in code) to others that might want to create apps, but doesn’t have access argo-cd directly to add a new app. These individuals might test apps from various branches that they’d create. So, how would you nest app of app of apps….?

I am trying to use ArgoCD notification to my Teams channel, but it isn't sending notification. So, I followed documentation here
I created an Incoming Webhook in teams and get URL
I set it to argocd-notification secrets:
Then I set up config map:
Then I subscribe it from application:

apiVersion: <http://argoproj.io/v1alpha1|argoproj.io/v1alpha1>
kind: Application
metadata:
  name: dreambook-argo-application
  namespace: argocd
  annotations:
    <http://notifications.argoproj.io/subscribe.on-sync-running.teams|notifications.argoproj.io/subscribe.on-sync-running.teams>: ArgoCD
    <http://notifications.argoproj.io/subscribe.on-deployed.teams|notifications.argoproj.io/subscribe.on-deployed.teams>: ArgoCD
    <http://notifications.argoproj.io/subscribe.on-health-degraded|notifications.argoproj.io/subscribe.on-health-degraded>: ArgoCD
spec:
  project: default
  source:
    repoURL: myrepo url
    targetRevision: HEAD
    path: dev/deployment
  destination:
    server: <https://kubernetes.default.svc>
    namespace: myns
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - Validate=false
      - Prune=true
      - SelfHeal=true
apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-notifications-cm
data:
  context: |
    argocdUrl: <https://20.204.207.96>
  trigger.on-health-degraded: |
    when: app.status.health.status == 'Degraded'
    send: [app-on-health-degraded]
  trigger.on-deployed: |
    when: app.status.operationState.phase in ['Succeeded'] and app.status.health.status == 'Healthy'
    oncePer: app.status.sync.revision
    send: [app-sync-succeeded]
  service.teams: |
    recipientUrls: 
      ArgoCD: $channel-teams-url
  template.app-on-health-degraded: |
    email:
      subject: Application {{.app.metadata.name}} has degraded.
    message: |
      Application {{.app.metadata.name}} has degraded.
      Application details: {{.context.argocdUrl}}/applications/{{.app.metadata.name}}.
    teams:
      facts: |
        [{
          "name": "Sync Status",
          "value": "{{.app.status.sync.status}}"
        },
        {
          "name": "Repository",
          "value": "{{.app.spec.source.repoURL}}"
        }
        {{range $index, $c := .app.status.conditions}}
          {{if not $index}},{{end}}
          {{if $index}},{{end}}
          {
            "name": "{{$c.type}}",
            "value": "{{$c.message}}",
          }
        {{end}}
        ]
      potentialAction: |
        [{
          "@type":"OpenUri",
          "name":"Open Application",
          "targets":[{
            "os":"default",
            "uri":"{{.context.argocdUrl}}/applications/{{.app.metadata.name}}"
          }]
        },
        {
          "@type":"OpenUri",
          "name":"Open Repository",
          "targets":[{
            "os":"default",
            "uri":"{{.app.spec.source.repoURL | call .repo.RepoURLToHTTPS}}"
          }]
        }]
      title: Application {{.app.metadata.name}} has degraded.

  template.app-sync-succeeded: |
    teams:
      facts: |
        [{
          "name": "Sync Status",
          "value": "{{.app.status.sync.status}}"
        },
        {
          "name": "Repository",
          "value": "{{.app.spec.source.repoURL}}"
        },
        {
          "name": "Revision",
          "value": "{{.app.status.sync.revision}}"
        }
        {{range $index, $c := .app.status.conditions}}
          {{if not $index}},{{end}}
          {{if $index}},{{end}}
          {
            "name": "{{$c.type}}",
            "value": "{{$c.message}}",
          }
        {{end}}
        ]
      potentialAction: |-
        [{
          "@type":"OpenUri",
          "name":"Operation Application",
          "targets":[{
            "os":"default",
            "uri":"{{.context.argocdUrl}}/applications/{{.app.metadata.name}}"
          }]
        },
        {
          "@type":"OpenUri",
          "name":"Open Repository",
          "targets":[{
            "os":"default",
            "uri":"{{.app.spec.source.repoURL | call .repo.RepoURLToHTTPS}}"
          }]
        }]
      title: New version of an application {{.app.metadata.name}} is up and running.
 
apiVersion: v1  
kind: Secret
metadata:   
  name: argocd-notifications-secret
stringData:
  channel-teams-url: mywebhookurl
type: Opaque
 

when i check the logs of argocd-notifications controller time="2023-05-26T01:44:34Z" level=info msg="Notification about condition 'on-created.[0].X_5TO4MPCKAyY0ipFgr6_IraRNs' already sent to '{teams

Hi! I'm troubleshooting a weird issue with ArgoCD while deploying the Grafana Helm chart on a Minikube test env.
For some reason the secret the chart generates is constantly being updated (specifically the admin-password key), resulting in the deployment to create a new replicaset and pod.

One would say this is an issue with their chart, but somehow I am seeing similar behavior with a different chart as well.

Any pointers on how to resolve this?

Hello folks, argo question.

I want to have an applicationset similar to this, the problem is that https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-files-discovery/apps/guestbook I dont want to store my helm chart here since I am using an helm chart repo.

Is there a way of using git generators with helm charts stored on a rempo rather than on a templates/ folder locally?

I’m using SAML with Okta and Dex. Any ideas on setting up argo-workflows to use argo-cd’s dex server?

Hi all, does anyone have any gitops / argocd repos that can give me some inspiration into how I should be organising the repo?

I'm managing around 20 clusters, that all use a combination of helm charts and vanilla k8s manifests. I'm trying to understand how best to organize my repo, and how best to use the apps of apps pattern to pull cluster specific workloads.

can any help me to impliment https://argocd-applicationset.readthedocs.io/en/stable/Generators-Pull-Request/
i dont have a problem with the applicationset side

i only need to see a the github action related ci flow, to see how it is best to create the whole flow, docker build and run tests on the new temp env

Hello, anyone using argocd with ChartMuseum ? How did you handle auth? Thanks!

Hi all, we are hosting our helm charts in a helm repo. Wanted to quickly demo using argocd to handle making PR preview environments, but the tutorials I have found online seem to be geared around keeping helm charts in git. Has anyone had any experience with the use case I describe? Cheers

Hey all,

Does anyone have an opinion of whether to have a single HA setup of ArgoCD having a 1:many relationship with dozens of clusters & different environments?

We're considering have a single ArgoCD per environment that would manage roughly 1-6 clusters each.

hello,
here is a share of an experience with argocd
I have create an issue by deleting an application that was pending for sync ..
Delete will wait for the app sync indefinitely and app can't be update to fix the sync.
kubectl delete application will not work
to fix this deadlock :
kubectl get application -A
$ kubectl edit application appname -n argocd
then remove the finalizer
now delete the application with kubectl
kubectl delete application appname

I have found guidance here https://github.com/argoproj/argo-cd/issues/1329

This is a good video to understand argocd, https://www.youtube.com/watch?v=P57mY5Lv2qA 🙂

Quick question - when bootstrapping a kubernetes cluster (i.e. EKS) - how much needs to be added as service in order for argocd to be deployed, so it can take over the rest of the bootstrapping of the cluster?
Are things like ingress etc. required - or can argo potentially do most of the heavy lifting so I don't have to mange these things via a different tool (i.e. kubernetes or terraform).

@johntellsall has joined the channel

@geertn has joined the channel

I just made working ArgoCD RBAC with Azure Active Directory
Groups and ArgoCD application registration in Azure has been made with terraform.
I have used the ArgoCD documentation "Azure AD App Registration Auth using OIDC"
https://argoproj.github.io/argo-cd/operator-manual/user-management/microsoft/#azure-ad-app-registration-auth-using-oidc

@MattyB has joined the channel

@Andrey Devyatkin has joined the channel

Thanks for creating this channel, I have started one week ago using it in test ;)

@Pierre-Yves has joined the channel

@Patrick Jahns has joined the channel

@Roger has joined the channel

@Nathaniel Selzer has joined the channel

@Christian has joined the channel

@Roach has joined the channel

@Hao Wang has joined the channel

US Air Force Platform One’s program has a project called Big Bang that uses ArgoCD. One of my teammates is test driving it currently.

• https://www.linkedin.com/pulse/getting-started-air-forces-big-bang-gke-jamal-mahboob/?trackingId=CfrOfPusPeOiSwY7SfmA5Q%3D%3D
• https://dodcio.defense.gov/Portals/0/Documents/DoD%20Enterprise%20DevSecOps%20Reference%20Design%20v1.0_Public%20Release.pdf
• https://software.af.mil/dsop/services/
• https://p1.dso.mil/#/products/big-bang/

@Andrew Roth has joined the channel

@Vineet Gupta has joined the channel

@Mohammed Yahya has joined the channel

@Ievgenii Shepeliuk has joined the channel

@aaratn has joined the channel

@Igor Rodionov has joined the channel

@TBeijen has joined the channel

@Adam Blackwell has joined the channel

@Erik Osterman (Cloud Posse) has joined the channel