acoustic-carpenter-78188
10/29/2025, 12:37 AMFor image pull secrets, you have several options:
1 Interactive mode (prompts for registry, username, password):
$ flyte create secret my_secret --type image_pull
2 With explicit credentials:
$ flyte create secret my_secret --type image_pull --registry <http://ghcr.io|ghcr.io> --username myuser
3 Lastly, you can create a secret from your existing Docker installation (i.e., you've run docker login in the past) and you just want to pull from those
credentials. Since you may have logged in to multiple registries, you can specify which registries to include. If no registries are specified, all
registries are added.
$ flyte create secret my_secret --type image_pull --from-docker-config --registries <http://ghcr.io|ghcr.io>,<http://docker.io|docker.io>
Previously, the pulling of the secrets from docker was hidden behind the old union create imagepullsecret command, which would grab all your local logins and dump them to a temp file.
• Also there was an issue (not sure recently triggered by a backend change) with list secrets - it was infinite looping because the token didn't quite work. Switching to the per cluster token solves the issue.
flyteorg/flyte-sdkacoustic-carpenter-78188
10/29/2025, 12:37 AMacoustic-carpenter-78188
10/29/2025, 4:46 PM