https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
d
Copy code
export const cluster = new digitalocean.KubernetesCluster('cluster', {
  region: digitalocean.Regions.LON1,
  version: 'latest',
  nodePool: {
    name: 'default',
    size: digitalocean.DropletSlugs.DropletS1VCPU2GB,
    nodeCount: 2,
  },
});
I also tried destroying the stack and up-ing it again, same results when I run 
pulumi preview
Any suggestions?
b
@dazzling-sundown-39670 I’d suggest setting the version explicitly rather than latest as that could result in upgrading at any point
g
I think, might be wrong, that their API return the exact version that the cluster is running in including the patch number. So when Pulumi refreshes the state prior to calculating the preview it see different strings (1.18/latest vs 1.18.x). For the API setting 1.18 means the latest 1.18.x, which is already set, but for Pulumi those are different strings If DigitalOcean applies patch updates automatically than maybe the provider should consider not updating x.y.z with x.y by checking the prefix. If they don't then the provider is correct it is trying to update to the latest patch every time. Using latest will always result in a update request as there might be new k8s versions available.
d
Yeah the solution was to do 
version: '1.18.3-do.0',
instead of just 
1.18
Cheers
Open in Slack
PreviousNext
Powered by

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.

Powered by