argo technologies
Hii
purpose
The purpose of application is to connect source and destination by using sync policy
Sync An Application is sync means, equalizing what is there in the cluster with what is there in GitHub OutOfSync - The application details what is there in the cluster are not equal to Github sync - The application details what is there in the cluster are equal to Github
all possible fields of an application yaml https://argo-cd.readthedocs.io/en/latest/user-guide/application-specification/
example repo for practice https://github.com/argoproj/argocd-example-apps
** ERRORS 1) Failed sync attempt to 2d5aa1bd2cf03a658ad355edc1002d01b394ff53: one or more objects failed to apply, reason: ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal string into Go struct field ConfigMap.data of type map[string]string (retried 5 times).
Solution: There is no space between : (colon) and value Wrong key:value1 Right: key: value1
SharedResourceError ConfigMap/game-demo is part of applications argocd/application and argocdin 2 minutes ago (Fri Jun 28 2024 17:17:40 GMT+0530) dont deploy any kubernetes resouce to the same cluster and same namespace using two different Applications. Solutions: Remove one of the Applications.
-
Unable to create application: application spec for APPNAME is invalid: InvalidSpecError: Unable to generate manifests in mbe-mainchart/dev: rpc error: code = Unknown desc =
helm template . --name-template APPNAME --namespace default --kube-version 1.26 <api versions removed> --include-crds
failed exit status 1: Error: release name "APPNAME": invalid release name, must match regex ^a-z0-9?(.a-z0-9?)*$ and the length must not be longer than 53
solution: give application name in all lowercase alphabet and numbers, can have a hyphen- in-between do not use any other characters -
Unable to create application: existing application spec is different, use upsert flag to force update
solution: Do not create application with the same name as an existing one.
Definition
- Prune when file is deleted in GitHub and corresponding resource still exists in k8s