jeremyjpj0916

@chronolaw looks like the source ends up in: ``` /usr/local/openresty/lualib/resty/events/* ``` Path for a traditional Kong bazel build image I have. I can just add to the image to dump...

Patch files added to dev w the smaller db, initial runtime looks good here: ``` 2024-06-26T16:11:48.650551282-05:00 nginx: [warn] the "user" directive makes sense only if the master process runs with...

Same issues persist even with the 0.3.0 patch files dropped in with the bigger DB(stage database) and resources: ``` 2024-06-26T16:33:36.307545718-05:00 nginx: [warn] load balancing method redefined in /usr/local/kong/nginx.conf:129 2024-06-26T16:33:38.088352910-05:00 2024/06/26...

Also if yall want me to hack any debug statements into the code to get a better understanding of whats happening I can. Just gotta give me the lines you...

@chronolaw thanks for staying on top of this error that preventing us from moving to newest Kong thus far. Do you have any opinion on if this is something safe...

Sounds good then to proceed and just ignore the errors if they start early but stop right after kong startup. Will continue with upgrading our Kong instances then in production...

Good stuff, hopefully yall can reproduce it.

And my resolv.conf default which seems to be what Kong ends up using during parts of the runtime when it should not: ``` ubuntu@kong-d4dfc6949-7wx2j:/$ cat /etc/resolv.conf search my-gateway-dc.svc.cluster.local, svc.cluster.local, cluster.local,...

@chobits sounds good, as long as you see in the warming up dns entries bit its not respecting the environment variable overrides w the dns client debug logs like shown...

@chobits in our k8s environment in my company seems like /etc/resolv.conf gets set by the platform on pod/container startup. Its nice to be able to see the difference in performance...