We released https://github.com/pulumi/pulumi-kubernetes/releases/tag/v1.2.2 today, which should greatly improve the performance of Pulumi stacks that include many Kubernetes resources! (70+% improvement on a benchmark Istio stack we profiled) Additionally, we removed the

<http://pulumi.com/intialApiVersion|pulumi.com/intialApiVersion>

annotation that was added in version

1.2.0

. Resources that were already updated to include this annotation will not be updated to remove it, but it is no longer in use by the provider. See the changelog for full details.

According to the release notes there's no support for 1.13. Is that actually true? We're still on 1.13 on AWS.

While the provider should continue to work for older versions, we don’t officially support them. This matches upstream’s support policy: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions Basically, this means that fixes will not be a priority for any bugs that only apply to unsupported k8s versions. Practically speaking, I haven’t seen any bugs like that since k8s 1.6, so it may not be an issue. Keep in mind that our SDK is generated from k8s’ OpenAPI schema, and it’s possible/likely that they will remove unsupported apiVersions once they roll out of the support window. For the apiVersions removed in 1.16, that would likely be the 1.18 release (~March 2020). At that point, you’d need to be on a version in the support window, or stop tracking current pulumi/kubernetes releases.

AWS EKS runs quite a bit behind the tip of Kubernetes. The latest version we can currently move to is 1.14. We (and your other users) have no control over when AWS upgrades. Please keep that in mind.

👍 We’ll certainly keep that in mind. The goal is to maintain support as broadly as possible, and we will reevaluate our support policy if it starts to cause problems for a lot of users (e.g., with EKS).

In the same boat @incalculable-engineer-92975