as you may know, Next.js generates static pages when creating a Docker image, so NEXT_PUBLIC are backed in JS files when creating the image. only dynamic pages can grab env variables via k8s yaml files when spinning up.

@tafutada777 any way to over come this? i tried addind the runtimeconfig to the nextjs-congif and try accessing is in in the file even that didnt work

basically, statically generated files are static, supposed to be cached on CDN edge servers across countries. in general, cached files need to be purged to update them. i use GCP k8s, docker images need to be copied and run immediately to minimize cold start time, then update load balancer routing to switch traffic.
say, suppose that if we have NEXT_PUBLIC_XXX to point to GraphQL server, we could get the endpoint dynamically via an API, like www.nextjs.server/getGraphQLURL in useEffect(). i guess.