Yeah, I’ve suggested in the past that maybe Pulumi should take over that. ALB is integral and doing it outside is such a shame and error prone. Especially with weakly typed yamls.

sorry—to clarify, the ALB is created on your behalf by EKS, when you use a Kubernetes resource like

Service

. If Pulumi interceded on your behalf it would almost certainly break something.

The kube controller in general expects to have total control of this resource.

happy to explain more in a thread—I was the original author of the kube stuff so I know it really well.

@creamy-potato-29402 Yeah, but it should be a different approach than using the ALB ingress controller. Setting up ALB with pulumi and point it to a serice or an ingress.

I think I've found a bug and reported it here. https://github.com/pulumi/pulumi/issues/3748 If someone could give it a once over for anything obviously stupid (always a possibility!), it would be appreciated.

you can definitely use other ingress controllers. Contour provides Envoy-based load balancing, and nginx-ingress does, well, what it says on the box.

in general this is totally pluggable.

not sure I understand this second comment though.

The second comment is how it works today with the ALB ingress CRD. That’s the selling point of it, is that it bypasses k8 and connects ALB directly by keep tracking the pods and nodes and connecting the ALB directly. The approach I am suggesting is a little bit more “inferior” since it goes ALB -> K8 -> Nodes -> Pods

Is there a way to get pulumi version programmatically, thinking of using it for tagging AWS resources.

Also, is there a way to set configs programatically?

can pulumi compare the local/remote state against actual resources before it apply the changes?

i created a resource(kubernetes configmap) using pulumi and deleted 'em manually.. when i tried to apply pulumi again, it says nothing to update

i remember reading some blog post that says pulumi compares the state with actual resources before it apply

apprently i don't remember where i saw that, but tried to find in pulumi doc.. i don't see anything such

One of my Pulumi stacks is configured to fetch a helm chart from a repo. The repo is in an S3 bucket and using the s3 helm plugin. This works great when everything lives in

us-west-2

, the same region as the helm repo. However, when I try to run the stack when AWS_REGION=ap-northeast-1 I get an error while fetching the helm chart:

fetch from s3: fetch object from s3: BucketRegionError: incorrect region, the bucket is not in 'ap-northeast-1' region at endpoint ''

On the commandline I can prefix my helm fetch command like this:

AWS_REGION=us-west-2 helm fetch...

The pulumi code looks like this:

export const splunkForwarder = new k8s.helm.v2.Chart("splunk-forwarder", {
    repo: "my-repo",
    version: "0.2.343",
    chart: "splunk-forwarder",
    namespace: namespaceName,
    values: forwarderValues,
}, { dependsOn: [loggingNamespace, cluster], providers: { kubernetes: cluster.provider } });

How can I tell it to use the

us-west-2

region for the helm fetch and to use the configured

ap-northeast-1

for all other resources?

Do anybody know how to add DNS record for 'ALB-Ingress-Controller' ?

Question - How to get this url e9275192-syngentaplatform--87b5-1276037906.us-east-1.elb.amazonaws.com as variable? I think, I need to pass it for creating Route53 DNS records.

const router = new k8s.networking.v1beta1.Ingress(
  'syngenta-platform',
  {........}
}

I am trying to figure out why routing is not working. Seems like some issue on the node.

Hello everybody, trying to reach the Sign in page on site (Pulumi). Can not sign in.. page is blank and only Chat is available

Working now...

@late-printer-99022 You can get the ingress endpoint with pulimi, I haven’t tested it myself yet, but planning to.

@flat-insurance-25294 any idea, about why is it showing unhealthy ?

Are your pods unhealthy?

Pods are working fine. It respond to any url with 200 OK

I checked using port forward too

What kind of health checks is your ALB hitting?