Payload is not working in k8s

[rainfall-manasi]

Describe the Bug

Hi Team am trying to deploy payload on k8s i have deployed my dev setup of payload dockerised and same setup have cloned in to my prod and build docker, and deployed via k8s. My welcome page is coming however on admin page am getting error on deployment logs kubectl logs -f payload-prod-6769f8c47b-vxqb6

payload-mongo@1.0.0 start /app
cross-env NODE_OPTIONS=--no-deprecation next start

▲ Next.js 15.4.4

• Local: http://localhost:3000
• Network: http://10.244.7.164:3000

✓ Starting...
✓ Ready in 512ms
[07:26:20] WARN: No email adapter provided. Email will be written to console. More info at https://payloadcms.com/docs/email/overview.
⨯ TypeError: Missing parameter name at 5
at (.next/server/chunks/3092.js:1:2720)
at (.next/server/chunks/3092.js:1:3397)
at g (.next/server/chunks/3092.js:1:4627)
at e (.next/server/app/(payload)/admin/[[...segments]]/page.js:243:11668)
at (.next/server/app/(payload)/admin/[[...segments]]/page.js:135:179368)
at Array.find ()
at (.next/server/app/(payload)/admin/[[...segments]]/page.js:135:179347)
at aq (.next/server/app/(payload)/admin/[[...segments]]/page.js:135:181592) {
digest: '2480943139'
}
⨯ TypeError: Missing parameter name at 5
at (.next/server/chunks/3092.js:1:2720)
at (.next/server/chunks/3092.js:1:3397)
at g (.next/server/chunks/3092.js:1:4627)
at e (.next/server/app/(payload)/admin/[[...segments]]/page.js:243:11668)
at (.next/server/app/(payload)/admin/[[...segments]]/page.js:135:179368)
at Array.find ()
at (.next/server/app/(payload)/admin/[[...segments]]/page.js:135:179347)
at aq (.next/server/app/(payload)/admin/[[...segments]]/page.js:135:181592) {
digest: '2480943139'

Link to the code that reproduces this issue

github

Reproduction Steps

unable to understand what is not working

Which area(s) are affected? (Select all that apply)

area: ui

Environment Info

prod env. on premise

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload