https://pulumi.com logo
#kubernetes
Title
# kubernetes
c

curved-doctor-83600

07/04/2021, 2:38 PM
Hi, today I updated the "values" part of a helm chart (v3) I deployed with pulumi, but pulumi didn't notice any change, therefore reported "everything unchanged". Is this a known limitation or should I dig deeper to (maybe) reveal an issue?
I effectively try to make sure, X-Forwarded* headers are sent to the services in k8s through the ingress. I tried to update the ingress-nginx helm chart values: values:     {        .// other settings..,         proxySetHeaders: {             "X-Forwarded-For": "$proxy_add_x_forwarded_for;",             "X-Forwarded-Proto": "$scheme;"         }     }}, // ... but pulumi didn't recognize that change. I then also tried to add some annotations to the ingress defined for a specific service, using the configuration-snippet annotation (https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#configuration-snippet), but without success. Can anyone point me into a direction how to find out how to perform the configuration to make the ingress-nginx set the X-Forwarded* headers? Thanks 🙂
p

proud-pizza-80589

07/05/2021, 3:49 PM
if this happens to me, i used a wrong key. if the values do not change the generated yaml, it does nothing.
for ingress-nginx, i often mess up for what goes under controller or top level.
what i do now is i convert the values file to json https://transform.tools/yaml-to-json and then json to a ts type https://transform.tools/json-to-typescript with a little bit of cleanup you gain ts validation
c

curved-doctor-83600

07/06/2021, 9:05 AM
Thanks for your suggestion, Roderick. This is definitely a smart way I will use more often in future. I was able to solve my original issue by providing a configmap for the ingress. Will nevertheless try your suggestion to verify if I messed up the values section.
4 Views