my nodejs based image has container port 3000 but target port is 80. as shown in code.

How about you make a smaller project without all that cruft, with just 200, hello world and make that works first?

container port doesn’t actually do anything, if you’re referring to the docker image

EXPOSE

. That’s just for documentation really.

Remove the healthcheck to see if it works, but you really should just make a hello world playground first

This is the smaller project with 2 services and each point to some route like /service1 and /service2 that is all the POC i am doing. POC: 1. Create Cluster - done 2. Run 2 Docker image - 1 create actual service and another is just ngnix - done 3. Run a ALB Ingress controller to route traffic , http://<ALB URL>/ngnix, http://<ALB URL>/ndvi, - pending 4. Add DNS record , http://api.syn-platform.com - pending 5. Make it work with

https

too - pending

Make an even smaller PoC because obviously you want to make sure the ALB works first.

kubectl logs --namespace kube-system $(kubectl get po --namespace kube-system | egrep -o [a-zA-Z0–9-]+alb-ingress[a-zA-Z0–9-]+)

Check errors as well.

no error

@flat-insurance-25294 - just found that- the NGNIX Service Target group is healthy but ndvi service is unhealthy !

Seriously stop code dumping, lol.

You told not to dump code. but not for logs. you mean don't dump log and code both ! 🙂

@flat-insurance-25294 can you verify following at-least

> KUBECONFIG=./kubeconfig.json kubectl get svc --all-namespaces

syngenta-platform   syngenta-platform-ndvi    NodePort    172.20.135.178   <none>        80:30603/TCP    4d12h
syngenta-platform   syngenta-platform-nginx   NodePort    172.20.233.206   <none>        80:30177/TCP    4d12h

it is showing port

80

in both case. is it correct? nginx service has container port 80 and target port 80, but ndvi service has container port 3000 and target port is 80.

unfortunately, the example by @narrow-area-11460 show 2080-game and all ports are 80. in real life, our docker container runs on something which is not 80.

so, it may be the issue with my configuration.

@flat-insurance-25294 problem solved , Instances are showing healthy now.

nice,

but I am stilling getting error like

E0115 10:45:08.543340       1 :0] kubebuilder/controller "msg"="Reconciler error" "error"="failed to reconcile targetGroups due to failed to reconcile targetGroup targets due to Unable to find http port on service syngenta-platform-ndvi"  "controller"="alb-ingress-controller" "request"={"Namespace":"syngenta-platform","Name":"syngenta-platform"}

in Ingress logs, but my Service is working fine.

Questions - Why dualstack is added in route53 on Route53 AWS UI it is showing me as - dualstack.e9275192-syngentaplatform--87b5-1276037906.us-east-1.elb.amazonaws.com. but in LoadBalancer url is - e9275192-syngentaplatform--87b5-1276037906.us-east-1.elb.amazonaws.com what is the difference? both gives exactly same response !!

export let ingressUrl = router.status.loadBalancer.ingress[0].hostname;

I have tried pulumi.interpolate and .apply syntax but I cannot get it working. I want to get ZoneId of

url

, I got the relevant code too but it is showing error like

Argument of type 'Output<string>' is not assignable to parameter of type 'string'

😞 I have take sample code from - https://github.com/pulumi/examples/blob/master/aws-ts-static-website/index.ts

Hi, in pulumi is there the concept of project level configs? Or do I have to rely on creating some kind of common stack that would hold common settings?

Hi Pulumi Community, I am at final round in PoC. My Ingress Code is here. https://gist.github.com/nsisodiya/d3535c78c8c95499b7efcd5805f8bda7 I want to create A record for ingress url. It involve getting ZoneId and code is faling. most of the time when I want to operate over

Output<string>

I am always stuck. Can someone help by looking at code. @flat-insurance-25294 - gist and not code dump this time 😉

Jesus dude, you didn’t even bother to format and indent. Why are you trying to create an A record? What’s the purpose?

What you want is an alias.

Hi Pulumi community! I can give some feedback for those of you who are interested in creating a mixed GKE cluster. Even though pulumi is perfectly capable of creating a "windows" node pool (you only need to change the image type),

node_config={
    'imageType': 'WINDOWS_SAC',

windows pool is currently an early access feature and you have to send your application to GCP . Please find the link to apply below: https://cloud.google.com/blog/products/containers-kubernetes/how-to-deploy-a-windows-container-on-google-kubernetes-engine https://docs.google.com/forms/d/e/1FAIpQLSfk6PAxUqQ0k08ByqU49yy8s1sLNivHLkbQ6ltxUZf49j3C0g/viewform

Hey Pulumi Community! I am curious if there is a Rancher 2 provider just like there is for other terraform providers today? We would like to switch to using Pulumi and I think this is the only provider I was unable to find in the docs.

Hi everyone! Is it possible to have a bi-directional dependency between two resources in Pulumi? For example: • Some resource X needs an input from an Azure App Service • The Azure App Service needs an app setting created with an output value from resource X Manually (if I were to do everything in the Azure Portal) I would do this by creating the App Service first, then resource X, then going back to the App Service to add the app setting and its value from some property of resource X. Is the same possible in Pulumi?

i'm doing a

pulumi.interpolate

on a string, and in the preview it showed the full string with

[secret]

where a variable would be, which was declared with

config.requireSecret

. then i decided to manually mark another interpolated variable (of type

pulumi.Output<string>

) as secret with

pulumi.secret(variable)

. that caused the entire string to become

[secret]

, so i don't get to see my config string with only the secret bits blacked out. is there a way to have that happen?

The

id

of a Gitlab

Group

resource is a string. In Gitlab, you can nest groups by setting the

parentId

, but this one is typed

number

. https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gitlab/#Group-id https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gitlab/#Group-parentId Is this something which could be aligned by regenerating the TF wrapper?

Meanwhile, how can I convert the

id: Output<string>

of my parent group to an

number | Promise<number> | OutputInstance<number>

which I can use as input for the

parentId

of my child group?