Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
m
millions-judge-24978
01/28/2020, 11:33 PMDid @pulumi/eks
0.18.19b
breezy-hamburger-69619
01/29/2020, 2:13 AMYes v0.18.19 was released yesterday. Though the changelog doesn’t reflect that - it has a typo that we're fixing.
Is there anything else that you're experiencing with the release?
m
millions-judge-24978
01/29/2020, 2:58 PMIt seemed to introduce a fair amount of flux that I thought maybe shouldn’t be a patch version but I didn’t look too carefully what changed.
A lot of changes in my
planb
breezy-hamburger-69619
01/29/2020, 3:46 PMSorry we introduced more changes than you were expecting. Our CI has been experiencing issues and we’ve been working to get it in a state to cut a release since it had been a while.
What changes did you see? What version were you updating from?
You could DM me the statefiles before and after, or email me them if you’d prefer (mike@pulumi.com), so that we can evaluate further.
Also, please feel free to open up any issues you’re encountering [1]. It is likely that if you’re seeing flux, so are others.
1 - https://github.com/pulumi/pulumi-eks/issues/new
m
millions-judge-24978
01/29/2020, 3:49 PMI’ll have to look into it in more detail when I have time, for now I just had to revert versions, I will make sure to open an issue if anything seems wrong, thanks!
👍 1
I’m just now having a chance to look into this. I’m seeing that the
kubeconfig├─ infrastructure:k8s-cluster-v2 cluster-us2
│ └─ eks:index:Cluster cluster-us2
~ │ ├─ aws:ec2:SecurityGroup cluster-us2-eksClusterSecurityGroup update [diff: ~tags]
~ │ ├─ aws:eks:Cluster cluster-us2-eksCluster update [diff: ~tags]
~ │ ├─ aws:ec2:SecurityGroup cluster-us2-nodeSecurityGroup update [diff: ~tags]
~ │ ├─ pulumi-nodejs:dynamic:Resource cluster-us2-vpc-cni update [diff: ~__provider,kubeconfig]
+- │ ├─ pulumi:providers:kubernetes cluster-us2-eks-k8s replace [diff: ~kubeconfig]
+- │ ├─ kubernetes:core:ConfigMap cluster-us2-nodeAccess replace [diff: ~metadata,provider]
+- │ ├─ aws:ec2:LaunchConfiguration cluster-us2-nodeLaunchConfiguration replace [diff: ~userData]
~ │ ├─ aws:cloudformation:Stack cluster-us2-nodes update [diff: ~tags,templateBody]
+- │ └─ pulumi:providers:kubernetes cluster-us2-provider replace [diff: ~kubeconfig]I did a targeted apply of just the things with
~tagsb
breezy-hamburger-69619
01/31/2020, 1:13 AMWhat version where you upgrading from to 0.18.19?
Did you happen to do a
pulumi refreshSupport for cluster tags were added, so that would apply.
Is the cluster still functional?
m
millions-judge-24978
01/31/2020, 1:15 AMFrom
0.18.18refreshYeah it is all fine now.
b
breezy-hamburger-69619
01/31/2020, 1:16 AMI believe the changes you experienced are related to refreshing the state of the live cluster.
Please let us know if you experience any further issues
m
millions-judge-24978
01/31/2020, 1:16 AMSure, thanks!