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

Serverless is a bit of a misnomer, since there is still some infrastructure needed to run your code, but it's invisible to you. AWS, Azure and GCP have their own managed solutions to achieve that. For a local Kubernetes cluster you do have to worry and manage it yourself.

There are some solutions to have the same serverless computational capabilities on Kubernetes, but I don't think any of them are official, thus no Pulumi support.

Thank you <@U013QM2EK7Y>, by “exploring serverless” I want to learn and understand for myself in how far I can shield or abstract the infrastructure away from my role as a developer. It is clear, that there is always infrastructure involved and in the end, everything runs on bare-metal. Due to our clients-nature, it is not possible to use any public clouds. I have to stay in a local environment and was hoping to find and use the same level of abstraction.

I've been away from Kubernetes for a while now, but I remember that Kubeless being regarded as the go-to serverless framework for Kubernetes.

If Pulumi handles Kubernetes objects OK, then it should be possible to achieve what you want.

Thanks for the hint with kubeless, I will do some research on it. But basically, I would write my own abstractions using Pulumi in case I stay with k3s by using the Kubernetes-plugin and so on. Is my understanding correct?

I've done a little experiment in wrapping a terraform provider for kind:
<https://github.com/pawelprazak/pulumi-kind/>

just an experiment right now so no packaged published

but I've also used pulumi with regular kind

```kind create cluster --config kind.config.yaml```

with `kind.config.yaml`:
```kind: Cluster
apiVersion: <http://kind.x-k8s.io/v1alpha4|kind.x-k8s.io/v1alpha4>
nodes:
  - role: control-plane
  - role: worker
  - role: worker```


then just point the provider to it:
```const kindContext = "kind-kind"
const kindProvider = new k8s.Provider(kindContext, {
    context: kindContext
})```


and use normally:
```const ns = new k8s.core.v1.Namespace(
    nsName,
    {
        metadata: {
            name: nsName,
            labels: {
                name: nsName,
                app: appName
            }
        }
    },
    { provider: kindProvider },
)```

btw. if there are any ts/js devs here and want to drop a PR or issue in my pulimi-kind repo on how to publish to npm, then it would be appreciated (I'm new to node)