This message was deleted.

sparse-intern-71089

09/11/2023, 8:58 AM

This message was deleted.

full-eve-52536

09/11/2023, 1:24 PM

That doesn't sound right to me. Could it be that your kubernetes yaml files are not set up right? Possibly the `imagePullPolicy` config?

able-painter-57976

09/11/2023, 1:42 PM

Hi,

imagePullPolicy

is ok. I use

Always

but common problem for deploying something with

latest

tag is that k8s does not recognize the change as manifests are the same. My question may state if pulumi has something to solve this issue, but as I think about it can't as this is based on k8s structure and declarative definitions in manifests.

cuddly-computer-18851

09/11/2023, 11:51 PM

https://kubernetes.io/docs/concepts/containers/images/#:~:text=You%20should%20avoid%20using%20the,42.0%20and%2For%20a%20digest.

☝️ 1

cuddly-computer-18851

09/11/2023, 11:51 PM

Basically it's recommended not to use

latest

👍 1

full-boots-69133

09/12/2023, 1:05 AM

Depending on if you can query your registry from Pulumi you could do something like this (using AWS ECR):

Copy code

const imageDetails = aws.ecr.getImageOutput({
  imageTag: 'latest',
  repositoryName: 'company-name/my-service',
})

const image = pulumi.interpolate`${imageDetails.repositoryName}@sha256:${imageDetails.imageDigest}}`

assuming

imageDetails.imageDigest

does not include the

sha256:

suffix (I have not tested this). I have used this approach with Ansible + Cloudformation (with ECS) in the past and it worked well.

👍 1

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.