-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KubernetesProcessor No registry was set for the container image, so 'ImagePullPolicy' is being force-set to 'IfNotPresent'. #11917
Comments
/cc @geoand |
Hi, I can't reproduce this problem. What version of Quarkus are you using? |
i share you my code |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 7, 2020
When the container image group was being set to empty (which is allowed as a result of quarkusio#8139), then the registry was incorrectly being determined as not being set Fixes: quarkusio#11917
geoand
added a commit
that referenced
this issue
Sep 7, 2020
Fix incorrect ImagePullPolicy forced setting
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 8, 2020
When the container image group was being set to empty (which is allowed as a result of quarkusio#8139), then the registry was incorrectly being determined as not being set Fixes: quarkusio#11917
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 8, 2020
When the container image group was being set to empty (which is allowed as a result of quarkusio#8139), then the registry was incorrectly being determined as not being set Fixes: quarkusio#11917
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 8, 2020
When the container image group was being set to empty (which is allowed as a result of quarkusio#8139), then the registry was incorrectly being determined as not being set Fixes: quarkusio#11917
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
this warnning appears even though i put the 'property quarkus.container-image.registry' , so the kubernetes yml is not correctly generated
Expected behavior
Actual behavior
(Describe the actual behavior clearly and concisely.)
log.txt
Configuration
The text was updated successfully, but these errors were encountered: