Comments (11)
Images are usually skipped for either of the two reasons:
- There is no newer version of the image in the registry or
- The image is not part of the application
Can you try to raise log level to debug by setting log.level: debug
in argocd-image-updater-config
, and restart the pod? This should give us a little more hints.
from argocd-image-updater.
Hi @jannfis , I have enabled the debug log level.
I can see in logs, time="2020-11-20T11:11:00Z" level=debug msg="Image 'hello-kubernetes' seems not to be live in this application, skipping.
Application is using the image and I am able to access the application as well.
Any Leads would be highly appreciated.
from argocd-image-updater.
Can you please post the annotations for image updater you are using?
from argocd-image-updater.
Hi @jannfis ,
Please find the annotations, for Gituhub Packages,
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
annotations:
argocd-image-updater.argoproj.io/image-list: hello-kubernetes
argocd-image-updater.argoproj.io/hello-kubernetes.update-strategy: latest-first
argocd-image-updater.argoproj.io/hello-kubernetes.pull-secret: cpaasgitdockerhub
name: cpaascanary-updater-git
spec:
destination:
namespace: default
server: https://kubernetes.default.svc
project: default
source:
path: app-private-canary-GithubPackages
repoURL: https://github.com/nivedita-atci/argocd-example-apps
targetRevision: HEAD
from argocd-image-updater.
OK. argocd-image-updater.argoproj.io/image-list
should be a list of fully qualified image names.
Looking at the source for your application, it probably should be something like: argocd-image-updater.argoproj.io/image-list: hello-kubernetes=docker.pkg.github.com/nivedita-atci/argocd-example-apps/hello-kubernetes
Also, looking at your application source, you might want to let the image updater know which of the Helm parameters to set for updating the image. I think you could have success with argocd-image-updater.argoproj.io/hello-kubernetes.helm.image-spec: image.repository
, given you using the alias from the annotation above.
For more information, please refer to https://argocd-image-updater.readthedocs.io/en/latest/configuration/images/#assigning-aliases-to-images and https://argocd-image-updater.readthedocs.io/en/latest/configuration/images/#specifying-helm-parameter-names
from argocd-image-updater.
Thanks much for the leads, I could get the images are being considered to be updated now, getting,
"Could not get tags from registry: Get "https://docker.pkg.github.com/v2/nivedita-atci/argocd-example-apps/hello-kubernetes/tags/list\": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"GitHub Docker Registry needs login\"}]}\n")" alias=hello-kubernetes application=cpaascanary-updater-git image_name=nivedita-atci/argocd-example-apps/hello-kubernetes image_tag=1.8 registry=docker.pkg.github.com
from argocd-image-updater.
The Git Hub Docker registry requires authentication. In your configuration, but you have only configured a pull secret for a different registry.
from argocd-image-updater.
Here is ConfigMap file of Argocd-image-updater,
apiVersion: v1
items:
- apiVersion: v1
data:
accounts.image-updater: apiKey
argocd.grpc_web: "true"
argocd.insecure: "true"
argocd.server_addr: 20.54.135.45
log.level: debug
registries.conf: |
registries:
- name: GitHub Docker Packages
prefix: docker.pkg.github.com
api_url: https://docker.pkg.github.com
ping: no
credentials: dockerconfigjson-github-com
I am getting below error,
time="2020-11-23T08:37:10Z" level=debug msg="Using no version constraint when looking for a new tag"
alias=hello-kubernetes application=cpaascanary-updater-app image_name=nivedita-atci/argocd-example-apps/hello-kubernetes image_tag=1.8 registry=docker.pkg.github.com
time="2020-11-23T08:37:10Z" level=error msg="Could not set registry endpoint credentials: invalid credential spec: dockerconfigjson-github-com" .
Same credentials have been used while deploying the application and we are able to deploy the application using the image from GitHub packages. When configured the same creds in registries.conf, I am getting error saying couldnot set registry endpoint credentials.
Any Leads would be highly appeciated.
Many Thanks in Advance.
from argocd-image-updater.
time="2020-11-23T08:37:10Z" level=error msg="Could not set registry endpoint credentials: invalid credential spec: dockerconfigjson-github-com" .
You need to specify the pull secret in a fully qualified manner (refer https://argocd-image-updater.readthedocs.io/en/latest/configuration/registries/#specifying-credentials-for-accessing-container-registries).
For K8s secrets, the basic syntax is: <secret_type>:<namespace>#<secret_name>
, where <secret_type>
is either secret
for a normal secret, or pullsecret
for a secret in a classical pull secret format (with JSON contents).
from argocd-image-updater.
I'm closing this issue. Feel free to reopen if it hasn't been resolved from your PoV.
from argocd-image-updater.
Hello @nivedita-atci ,
I am having the same issue. Could you please let me know if you were able to get past this issue ?
from argocd-image-updater.
Related Issues (20)
- starts getting timeout errors with ECR registeries until pod is restarted HOT 1
- Request for "latest pushed tag" update strategy HOT 1
- Cache hit
- Could not update application spec: could not get creds for repo '': credentials for '' are not configured in Argo CD settings HOT 1
- Image updating firing every 10 minutes instead of default 2 minutes
- Provide more details about error if connection to argocd fails.
- After successfully updating the image, the Helm values passed in the application are reset HOT 3
- Git Write-Back Target annotation doesn't seems commits to the kustomization file back to source path
- Error fetching metadata from Docker Hub
- {{ .OldTag }} does not match actual old tag being replaced
- Update strategy: newest-build not working HOT 2
- image updater post-sync hook
- could not get tags: Get "https://myharbor.domain/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority
- the image updater wants to connect to 52.219.169.162 (s3-r-w.eu-central-1.amazonaws.com) HOT 2
- Issue with Authentication in ArgoCD Image Updater for Docker Hub
- golangci-lint context loading failed: no go files to analyze
- ArgoCD does not consider images for arch "linux/arm64/v8" HOT 1
- Sequential Builds Overwriting Image Tags in Git Repository
- Digest Update Strategy Incorrectly Adding "Latest" Tag
- Bug between v0.12.2 to v0.13.0 in git write-back implementation HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from argocd-image-updater.