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

it largely depends on your ingress controller, most don’’t support this. you’re better off exposing the service directly

+1 to what <@UCWG26BH7> said. Given the nature of SSH, I think exposing SSH directly is a better approach, if that’s at all possible for you.

Now, the question of why we are talking about SSH in the context of Kubernetes and an ingress controller is another story entirely… :rolling_on_the_floor_laughing:

&gt;  Is exposing ssh through ingress controller (or any non http/https service) a terrible idea?
Yes. You're probably going to have a bad time doing this with ingress controllers specifically. If you're interested in implementing a pattern similar to this, look into configuring envoy in Istio.