Channels
datahub-flyte
scipy-2023-workshop
flyte-school
agent-support-memverge
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
flyte-github
linkedin-flyte
random
deployment
hacktoberfest-2023
feature-discussions
linen-test
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#flyte-deployment
Title
a
Andrew Achkar
08/16/2022, 4:30 PM
Q: I noticed the flyte-core
helm charts reference
reference the
cr.flyte.org
container registry, but there are also equivalent images stored in the github container registry (eg.
https://github.com/flyteorg/flyteadmin/pkgs/container/flyteadmin
). Is there any downside to referencing the images in github container register as compared to
cr.flyte.org
? Are those registries different in any way?
s
Samhita Alla
08/17/2022, 5:06 AM
Hi,
@Andrew Achkar
! We use scarf.sh to fetch insights, and
<http://cr.flyte.org|cr.flyte.org>
is related to scarf. You’re free to use a registry of your choice!
a
Andrew Achkar
08/17/2022, 1:09 PM
Ok, that’s good to know. Thanks!
4 Views
Post