Skip to content
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

Closed
lvargas0584 opened this issue Sep 5, 2020 · 3 comments · Fixed by #11933
Assignees
Labels
area/kubernetes kind/bug Something isn't working
Milestone

Comments

@lvargas0584
Copy link

lvargas0584 commented Sep 5, 2020

Describe the bug
this warnning appears even though i put the 'property quarkus.container-image.registry' , so the kubernetes yml is not correctly generated

 - image: xxxx.dkr.ecr.us-east-1.amazonaws.com/business-command:1.0-SNAPSHOT
        imagePullPolicy: IfNotPresent
        name: business-command
        ports:
        - containerPort: 8080
          name: http
          protocol: TCP

Expected behavior

 - image: xxxx.dkr.ecr.us-east-1.amazonaws.com/business-command:0001
        imagePullPolicy: Always
        name: business-command
        ports:
        - containerPort: 8080
          name: http
          protocol: TCP

Actual behavior
(Describe the actual behavior clearly and concisely.)
log.txt

Configuration

com.app-name=${APP_NAME}
quarkus.package.output-name=${com.app-name}


# Log
quarkus.log.level=${LOG_LEVEL_ROOT:INFO}
#quarkus.log.category."io.smallrye".level=${LOG_LEVEL_ROOT:DEBUG}


#CLIENT SERVICIOS REST
data-core/mp-rest/url=http://data-core:8080


#DOCKER
quarkus.container-image.registry    =   xxxx.dkr.ecr.us-east-1.amazonaws.com
quarkus.container-image.build       =   true
quarkus.container-image.push        =   true
quarkus.container-image.name        =   ${com.app-name}
quarkus.container-image.tag         =   001
quarkus.container-image.group       =


#KUBE
quarkus.kubernetes.replicas=1
quarkus.kubernetes.part-of=core-app
quarkus.kubernetes.image-pull-policy=Always

@lvargas0584 lvargas0584 added the kind/bug Something isn't working label Sep 5, 2020
@quarkusbot
Copy link

/cc @geoand

@geoand
Copy link
Contributor

geoand commented Sep 5, 2020

Hi,

I can't reproduce this problem. What version of Quarkus are you using?

@lvargas0584
Copy link
Author

i share you my code
the quarkus version is 1.7.0

business-bemobi-ms.zip

@geoand geoand self-assigned this Sep 7, 2020
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
@gsmet gsmet added this to the 1.9.0 - master milestone Sep 7, 2020
geoand added a commit that referenced this issue Sep 7, 2020
Fix incorrect ImagePullPolicy forced setting
@gsmet gsmet modified the milestones: 1.9.0 - master, 1.8.0.Final Sep 8, 2020
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 gsmet modified the milestones: 1.8.0.Final, 1.7.3.Final Sep 8, 2020
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
Labels
area/kubernetes kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants