faint-motherboard-95438
01/28/2020, 10:35 AMIngress
in my clusters which was working fine before but now when I create/update I got an error like :
error: creation of resource […] failed because the Kubernetes API server reported that the apiVersion for this resource does not exist. Verify that any required CRDs have been created: no matches for kind “Ingress” in version “networking.k8s.io/v1beta1”I create the resource like
new pulumi_kubernetes.networking.v1beta1.Ingress()
I tried to switch to `pulumi_kubernetes.networking.v1.Ingress`but I got a type error that Ingress
does not exist in networking.v1
My versions :
“@pulumi/kubernetes”: “1.4.1",
“@pulumi/pulumi”: “1.9.0",
kubectl version :
Client Version: version.Info{Major:“1”, Minor:“17", GitVersion:“v1.17.2”, GitCommit:“59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:“clean”, BuildDate“2020 01 23T1421:54Z”, GoVersion:“go1.13.6”, Compiler:“gc”, Platform:“darwin/amd64”}
Server Version: version.Info{Major:“1", Minor:“13+“, GitVersion:“v1.13.11-gke.14”, GitCommit:“56d89863d1033f9668ddd6e1c1aea81cd846ef88", GitTreeState:“clean”, BuildDate“2019 11 07T1912:22Z”, GoVersion:“go1.12.11b4”, Compiler:“gc”, Platform:“linux/amd64”}
I suppose that’s a problem between pulumi packages version and the kubernetes server api but I can’t find a match between them both now.
I also tried to downgrade @pulumi/kubernetes
without any success.faint-motherboard-95438
01/28/2020, 11:01 AMextensions.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 ?stocky-island-3676
01/28/2020, 4:26 PMnetworking.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.faint-motherboard-95438
01/28/2020, 4:37 PM1.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
01/28/2020, 4:38 PMstocky-island-3676
01/28/2020, 4:45 PMpulumi-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.stocky-island-3676
01/28/2020, 4:47 PMpulumi-kubernetes
.faint-motherboard-95438
01/28/2020, 6:53 PMstocky-island-3676
01/28/2020, 7:05 PM