https://pulumi.com logo
Powered by
s

stocky-island-3676

10/08/2019, 8:23 AM
Changing the 
image
of a Kubernetes Deployment is not displayed as a change with 
pulumi up --refresh
. I changed it directly with 
kubectl edit
. The details view of 
pulumi up
shows that the 
image
will be refreshed in the stack, though. What do I do wrong? (The code is from 
pulumi new kubernetes-typescript
with fixed 
image
& 
minikube
provider.)
k8s_simple-change-detection-failure.ts
Simple test: 
kubectl edit deploy nginx-...
& change to 
image: nginx:1.16.1-alpine
`pulumi version`: 
v1.2.0
package.json
t

thousands-angle-40305

10/15/2019, 3:19 PM
@future-barista-68134 are you able to assist with this?
f

future-barista-68134

10/15/2019, 3:22 PM
Sure, I can take a look at this for you Dominik. Looks like you're trying to POC out the kubernetes functionality?
s

stocky-island-3676

10/15/2019, 3:27 PM
No, just created a MWE to test if it occurs there, as well. Do you get the same result? I stumbled upon this behaviour sometimes. Last while deploying 
kube-prometheus
which has many K8s resources.
I’m seeing the change in the details of the 
refresh
stage (either 
pulumi refresh
or 
pulumi up --refresh
). But I don’t see that 
pulumi up
doesn’t want to change the image back to what’s defined in the code, i.e. 
nginx:1.6.1
.
@future-barista-68134 I’ve found that this bug is already in an issue: https://github.com/pulumi/pulumi-kubernetes/issues/694
@microscopic-florist-22719 indicated that this is expected behavior with legacy diff because the kubectl scale command apparently doesn’t set the 
<http://kubectl.kubernetes.io/last-applied-configuration|kubectl.kubernetes.io/last-applied-configuration>
annotation.
The solution is to use the new Kubernetes provider option 
enableDryRun: true
(hint: there may be stability issues with it as mentioned in the Github issue).
f

future-barista-68134

10/21/2019, 5:51 PM
Okay, I've made the engineering team aware. Currently is there anything about using enableDryRun that will block you from your desired workflow for now?
s

stocky-island-3676

10/26/2019, 10:38 AM
@future-barista-68134 No, using 
enableDryRun
seems fine for now. Didn’t use it in bigger projects, yet. Currently working on other things. Sorry for the late answer. Just realized that I don’t get any notification from threads. Best is you always @mention me. Then it’s sure I’ll receive a notification.
👍 1
Powered by