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

<@UFX41J1CG> these docs come from the Kubernetes OpenAPI spec. It’s basically a `v1/List` of only `Service`s

yeah, i understand that, but how do I use it, lol

Confusingly, you can’t give it a `namespace` because it is not instantiated by the API server.

Typically `List`s are used to _return_ objects when you do a `kubectl get` for example

If you submit it _to_ the API server, it will instantiate everything _in_ the list, but not the list itself.

so i need to put something inside the items? but what?

whatever you’d pass to `new core.v1.Service`

how do I do it without pulumi creating the actual service?

I’m confused, what are you trying to do, now?

ok, like you said, list is used to retrieve stuff, right? I'm trying to find the external IP of the nginx ingress service, because its not being created by pulumi, its being created by a helm chart during cluster provisioning

It _can_ be used to retrieve stuff, but if you do `new ServiceList` with Pulumi, it tells Pulumi to create all the `Service`s inside.

`kubectl get svc` happens to return a `ServiceList`. But if you `kubectl apply` a `ServiceList`, it will create/update those `Service`s

ok, so this particular thing in python sdk is used to create services, not get them? so there is no method to get data from k8s in python sdk?

Come to think of it we should probably remove the `List` types. In practice I don’t think they’re useful in the context of Pulumi. In an `apply` they are really only useful if you have a single JSON document and you want to create a bunch of services.

I’m not sure, let me check if we implement `.get`

i dont think i see any gets in the reference

only list, i thought lists are for that =\

hmm, yes, this is an easy feature to add, we can probably fix this next week.

<https://github.com/pulumi/pulumi-kubernetes/issues/434>

ok, thanks. i guess I'll just wait for now :wink:

i'll use kubectl to retrieve it, probably