This message was deleted.

Ok that’s actually because I followed the warning to change

extensions.v1beta1.Ingress

to

networking.v1beta1.Ingress

which apparently did not work as expected. I reversed to

extensions.v1beta1.Ingress

and it’s working again. But that’s confusing, deprecation warning to replace apiVersion but the pulumi typing does not seem to know about them ?

@faint-motherboard-95438

networking.v1beta1.Ingress

was implemented in K8s version 1.14. Your K8s cluster is on 1.13. That’s why it didn’t work. See @orange-policeman-59119’s really good overview about K8s API resource changes: https://github.com/pulumi/pulumi-kubernetes/issues/919#issue-538623553 The error message is from the K8s API server, though.

@stocky-island-3676 thanks. that’s kind of difficult to stay up to date with all the permanent updating of version everywhere, moreover with Pulumi compatibility. Since my kubernetes server is still

1.13

pulumi should not raise a warning about something that is not relevant in the current cluster and is actually misleading, should it ?

@faint-motherboard-95438 That’s right.

pulumi-kubernetes

just recently supports also older versions down to 1.9. https://github.com/pulumi/pulumi-kubernetes/pull/911/files#diff-04c6e90faac2675aa89e2176d2eec7d8 Therefore there should be an error message & hints. Do you mind creating an issue there? Thanks.

Ok, I’ll open an issue. Sorry about the channel, I was here since the beginning and didn’t notice there’re new subchannels now.

Thanks. Can you post the link to the issue here for reference (when someone searches Slack and finds this one), please? No worries about the channel. That’s why I’m mentioning it.