[BUG] flyte-pod-webhook bind address already in use on startup

[hamersaw]

Describe the bug

When attempting to start a Flyte deployment using the official Flyte helm charts users are experiencing an error regarding failure to bind to the 8080 port:

{"json":{},"level":"fatal","msg":"Failed to create controller manager. Error: failed to initialize controller-runtime manager: error listening on :8080: listen tcp :8080: bind: address already in use","ts":"2022-09-14T22:11:13Z"}

Internally this is the port defaulted for the k8s controller-runtime manager, which is specified in the error message.

Expected behavior

The flyte-pod-webhook should start with no issue.

Additional context to reproduce

Currently unable to reproduce locally.

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes