Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hello! I am trying to use my private Docker Registry for node image, it is works in sandbox if executed ‘docker login’. But how it should be done on production cluster with Flyte? Tried to debug and found this line: <https://github.com/flyteorg/flytepropeller/blob/6a9c1d4490c94e993b9a859d15c3b436c98af3c2/pkg/apis/flyteworkflow/v1alpha1/nodes.go#L119> as i understand - Propeller is able to read K8s secrets from this field. But how to pass this field via Python FlyteKit? Can i pass them using raw container definition?

you will have to mount the credentials into your namespace -

just add the secrets to the `service account` and launch with that service account

<@U029U35LRDJ> <https://github.com/flyteorg/flytepropeller/blob/6a9c1d4490c94e993b9a859d15c3b436c98af3c2/pkg/apis/flyteworkflow/v1alpha1/nodes.go#L119|this> is what we need to get rid off from the CRD. These fields are useless

<@UNZB4NW3S> Could you please show example of such mount? <https://flyte-org.slack.com/archives/CNMKCU6FR/p1649692905694309?thread_ts=1649671829.478909&amp;cid=CNMKCU6FR>

hey <@U039MDSGQA2> you can use the cluster resource controller which is a cron process that manages and updates per-project k8s namespaces. You can use it to automatically to create <https://github.com/flyteorg/flyteadmin/blob/master/sampleresourcetemplates/docker.yaml|dockerhub secret> and add <https://github.com/flyteorg/flyteadmin/blob/master/sampleresourcetemplates/imagepullsecrets.yaml|ImagePullSecrets> to the default (or other) service account. Just add these linked template files to your helm deployment, like <https://github.com/flyteorg/flyte/blob/daec2a2e9ef7a4e973d241bb8936600c1c4b844d/charts/flyte/values.yaml#L631|here>

more background on the cluster resource controller and how to actually assign the templatized password in your deployment config can be found here : <https://docs.flyte.org/en/latest/deployment/cluster_config/general.html#cluster-resources>

let me know if this makes sense and if you want to chat more about this <@U039MDSGQA2>!

<@UNZB4NW3S> <@UPBBNMXD1> Thank you for the support!