No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

On 1 - that’s a good question for <@UE1LN7A22>. 

On 2 - you should be able to work with any CRD - though by default these will be loosely typed. <https://github.com/pulumi/pulumi-kubernetes/issues/219> is tracking one approach that we could take to provide strongly typed wrappers over arbitrary CRDs. 

For 1 — we don’t  have first-class support for any OpenShift-specific stuff. As Luke mentioned, CRDs are fully supported, but loosely typed. As for apiVersion support, we currently support the full API surface, including deprecated resources such as `apps/v1beta1:Deployment`, but can’t guarantee that will be true in the future. We follow the upstream model with first-class support for N-2 versions, which  currently means 1.14-1.16.

Short answer: standard k8s 1.11 stuff will most likely work as expected

Thanks <@UB3BGTV63> and <@UE1LN7A22> for explanation. For point 2 I’ll have a deeper look into this direction.
For point 1 - this question was “driven” by more and more warnings like:

```warning: extensions/v1beta1/Ingress is not supported by Kubernetes 1.16+ clusters. Use networking/v1beta1/Ingress instead.```
But I can’t follow the advice because the k8s cluster behind is on v1.13 which doesn’t know anything about `networking/v1beta1/Ingress`…
One workaround we have in mind is going back to older versions of k8s plugin. But we are not sure whether that’s a good idea - or not :wink:

You can suppress those warnings with a flag on a resource provider:

```const k8sProvider = new k8s.Provider("k8s-provider", {
  suppressDeprecationWarnings: true,
});```


That would be helpful -&gt; I’ll try it, Thnx <@UE1LN7A22>