pthornton
commented
2 years ago ApplicationSet that creates application for above chart:
---
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
name: react-frontend-service-test
labels:
ring: test
spec:
generators:
- git:
repoURL: https://gitlab.com/somewhere/prt/example-apps/mushu-dev.git
revision: HEAD
files:
- path: "config/**/config.json"
template:
metadata:
name: 'react-frontend-service-{{cluster.name}}'
labels:
ring: test
tenant: '{{cluster.name}}'
domain: '{{cluster.domain}}'
spec:
project: '{{argocd.project}}'
source:
repoURL: https://gitlab.com/somwhere/prt/example-apps/mushu-dev.git
targetRevision: HEAD
path: "./react-frontend-service/helm_base"
helm:
version: v3
releaseName: 'react-frontend-service-{{cluster.name}}'
valueFiles:
- ../overlays/{{cluster.name}}/globals.yaml
- ../overlays/flags.yaml
- ../overlays/{{cluster.name}}/values.yaml
- ../overlays/{{cluster.name}}/hotfix.yaml
destination:
server: '{{cluster.address}}'
namespace: 'example-test'
ignoreDifferences:
- group: apps
jsonPointers:
- /spec/replicas
kind: Deployment
namespace: 'example-test'
# Sync policy
syncPolicy:
automated: # automated sync by default retries failed attempts 5 times with following delays between attempts ( 5s, 10s, 20s, 40s, 80s ); retry controlled using `retry` field.
prune: true # Specifies if resources should be pruned during auto-syncing ( false by default ).
selfHeal: true # Specifies if partial app sync should be executed when resources are changed only in target Kubernetes cluster and no git change detected ( false by default ).
allowEmpty: false # Allows deleting all application resources during automatic syncing ( false by default ).
syncOptions: # Sync options which modifies sync behavior
- CreateNamespace=true # Namespace Auto-Creation ensures that namespace specified as the application destination exists in the destination cluster.
- Validate=true # disables resource validation (equivalent to 'kubectl apply --validate=false') ( true by default ).
hammeryx
AustinSmart
mfbieber
hedasaurabh
alexef
blakepettersson
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version.Describe the bug Application Chart:
All applications referencing AWS oci charts fail after upgrade. It appears "helm registry login" is only called when add the helm repo using "helm repo add" from cronjob. The "helm dependency update" fails and no login messages appear in repoServer logs.
Error message from UI:
Repo server log:
If I bash into the repo server and do "helm registry login" and then "help dependency build" in the /tmp/https___gitlab.com_somewhere_prt_example-apps_mushu-dev/react-frontend-service/helm_base folder, it successfully pulls the OCI helm chart. So no permission issues. I'm using username/password/url from the argocd cli helm repo add created kubernetes secret repo-4159968007.
This also happens if I upgrade to 2.1.7 instead of 2.2.2. Post in argocd slack also: slack
To Reproduce
Add Application using chart with reference to AWS OCI helm chart.
Expected behavior
Helm charts should pull from AWS OCI after successful "helm registry login" executed before running "helm dependency update".
Screenshots
If applicable, add screenshots to help explain your problem.
Version
Logs