Hi Flyte team 👋. How can I configure a different port for profiler started by cluster resource controller in flyteadmin deployment? https://github.com/flyteorg/flyte/blob/v1.15.1/flyteadmin/cmd/entrypoints/clusterresource.go#L37 Default profiler port 10254 is conflicting with the application when we run cluster resource controller as sidecar

Failed to Start profiling and Metrics server. Error, listen tcp :10254: bind: address already in use

I think you should be able to set that in your helm chart when deploying. Do you use the flyte-binary or the flyte-core deployment?

flyte-core, we deploy flyte components as separate services. Currently we are using flyte 1.15.1. What config can we specify to override profiler port? Can we do it via env variable? I tried setting env var

FLYTEADMIN_PROFILERPORT: 10255

, but that doesn't seem to work

Hi, I think you can try to fix flyte admin profiler port in the values.yaml here.

@faint-pilot-24699 We are not using the helm chart, but a custom starlark-based deployment. So can we configure the profiler port with an environment variable or an argument to

flyteadmin clusterresource run

command?

Hi @wonderful-continent-24967. The FlyteAdmin service init with flyte_admin.yaml file, which includes a profiler_port setting for user to configure. While executing FlyteAdmin with command, you can put a argument to specify the config file. You can refer to the make file for example command.😁