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

are you able to give me more information on what is planned for kubernetesx?

We haven’t started designing it yet, but it will be like awsx — just like the underlying API, but with a couple of little things that make it “richer”

stuff like `myDeployment.mountFile` vs creating a `ConfigMap` and adding it to a volume list.

Just a note here - the `awsx.ecs.Image.fromPath` is just a wrapper that creates an `ECR` repository and builds and pushes a local Docker image to it.  Effectively it just wraps these lines into a nice function: <https://github.com/pulumi/pulumi-docker/blob/master/examples/aws/index.ts#L18-L45>

You can use this as-is with Kubernetes if you want - or you can write similar code to work with whatever other registry you want to push to - DockerHub, GCR, ACR, or something you are self-hosting in your cluster - using `@pulumi/docker` directly.

You should not need any `kubernetesx` like thing for this (and in fact, because Kubernetes itself doesn't have any built-in registry, it's not immediately clear that a `fromImage` will be part of such a library).

thanks for the tip. can you give me an example of how i would implement this "as-is"?

i am trying to create a caddy server:
```
image: awsx.ecs.Image.fromPath("caddy", {
                                    dockerfile: "./src"
                                }),
```

unlike in the example on the pulumi website (which i guess is incorrect?), it seems `fromPath` in the latest version (0.16.5) requires 2 parameters. but i cant figure out how the second parameter needs to be specified. it would help if i could get an example.