UserSettings got generated and saved to: /home/node/.n8n/config
2020-11-25T16:08:05.785351185Z (node:6) UnhandledPromiseRejectionWarning: Error: There was an error: options.port should be >= 0 and < 65536. Received NaN.
2020-11-25T16:08:05.785421438Z at Object.error (/usr/local/lib/node_modules/n8n/node_modules/@oclif/errors/lib/index.js:26:15)
2020-11-25T16:08:05.785431156Z at Start.error (/usr/local/lib/node_modules/n8n/node_modules/@oclif/command/lib/command.js:60:23)
2020-11-25T16:08:05.785436947Z at /usr/local/lib/node_modules/n8n/dist/commands/start.js:134:22
2020-11-25T16:08:05.785442618Z (node:6) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
2020-11-25T16:08:05.785456193Z (node:6) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Think has to do with naming. If you call the service (can not remember the correct k8s right now) “n8n” it will automatically create a variable “<SERVICE_NAME>_PORT” so “N8N_PORT” which is the same environment variable n8n uses internally. That messes stuff up. If you give it another name that should solve that problem.
K8s sets its own set of env vars. So if the application is named “n8n” in kubernetes then k8s set the env var APPNAME_PORT resulting in N8N_PORT=tcp://10.37.21.70:80 which causes the error.