NiFi 2.0.0 Web Server Not Getting Correct IP After Upgrade from 1.27.0

[#1]

Hi Community,

I recently upgraded Apache NiFi from 1.27.0 to 2.2.0 in my Kubernetes environment. After the upgrade, I noticed that the web server is not getting the correct IP address in the logs, and my NiFi UI is not accessible.

Setup Details:

• Previous Version: NiFi 1.27.0
• Current Version: NiFi 2.2.0
• Deployment: Running in Kubernetes
• Logs Behavior:
  • In 1.27.0, the NiFi web server correctly binds to the expected IP.
  • In 2.2.0, the web server logs do not show the correct IP, and the pod eventually restarts after a few minutes.

Troubleshooting Done:

• Verified nifi.properties settings, including  nifi.web.https.host.
• Checked kubectl logs --previous but did not find any fatal errors before the restart.
• Ensured the container has enough memory and CPU.
• Checked for readiness/liveness probe failures in Kubernetes but found no failures.

Questions:

1. Has anyone faced a similar issue after upgrading to NiFi 2.2.0?
2. Are there any new configuration changes in 2.2.0 that could affect the web server binding/IP resolution?
3. Any additional logs or debugging steps I should check?

[#2]

@MattWho 

Could you please suggest here?

Really appreciate your insights here