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

This is for an ALB created by Kubernetes on your behalf?

Can you read `ingress.status.loadBalancer.ingress[0].hostname` off of the ingress object?

You mean using kube-query or by using a static get method on network/beta1/ingress?

I am actually considering creating ALB from pulumi instead and managing it manually but I am not sure what the consequences are.

I would rather prefer that as the alb-ingress project doesn’t let you name anything.
It makes using cloud watch custom metrics really tricky if you got multiple clusters with multiple ALBs.

I mean just from within your Pulumi program.  Get the `ingress` object that created with on your behalf (if it's from Helm, `getResource` on the chart).

If ALB Ingress allows your to bring-your-own-ALB, that definitely gives you much more control (I wish more Kubernetes things were like that).

Oh, I can access the ingress from the chart? I did not know that.

I see now, the ALB address is part of the ingress, and not the controllers.

<@UB3BGTV63> Well I mean, isn’t the custom resource ALB Ingress Controller technically just setting up an ALB and adding the nodes to it with some config?

Why couldn’t I just setup an ALB for my EKS without installing their helm charts?

<https://aws.amazon.com/blogs/opensource/network-load-balancer-nginx-ingress-controller-eks/>

<@UB3BGTV63>
Could you confirm wether or not creating an ingress and accessing   `status.loadBalancer.ingress[0].hostname`  is the same as calling `kubectl get ingress …` and reading the address on it?

Fyi you might want to update <https://www.pulumi.com/blog/kubernetes-ingress-with-aws-alb-ingress-controller-and-pulumi-crosswalk/>
as its using deprecated parts of the k8 extension.

Yes - reading ingress.status should be the same as reading the corresponding entry of kubectl get ingress. 

Was halfway through creating ALB from scratch over ClusterIP and an Ingress, lol.

Would you mind opening a GitHub issue in the pulumi/docs repo about the blog post?  (Including what there is deprecated?).

To be clear
```new k8s.extensions.v1beta1.Deployment```
is marked deprecated by you, not by K8.

In fact, everything under `k8s.extension`  is deprecated.

Yep - got it - thought you meant something in the ALB Ingress itself. 