-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Why is image not updated? #1504
Comments
Hi! Try this:
The container name is the name field in the pod spec, and I think you have to specify glob, other semver automation types |
OK my first problem was that I didn't understand to replace unfortunately that didn't work. I now have this:
And I have a number of master-xxx tags in docker hub that are later than master-c00edf01, however when I deploy it stays at I see in the log of flux:
so it looks like it wants to update the docker tag, but is reporting "no automated services", so maybe this annotation is incorrect?
|
What kind of resource does the YAML describe, just to check? You say "pod" and also "deployment". |
Here's the full yaml:
|
Now that I got |
That's a good idea; there's only a small section on how to use annotations, which could be its own document. |
In reference to fluxcd#1504
I set up a pod with a deployement yaml file like so:
I don't need to do anything more than deploy with the annotations to get it to update when a new docker image appears with a name like
master-*
, right?Is it a problem that I'm starting from the
latest
tag? If I put inmaster-nonexistent
and push that to the git repo, will it fail at first and then see that it's not the latest and update it appropriately? Or do I have to create amaster-latest
tag for that first installation?The text was updated successfully, but these errors were encountered: