Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-on-gcp
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
integrations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
show-and-tell
sig-large-models
torch-elastic
workflow-building-ui-proj
writing-w-sfloris
Powered by
Title
k
Ketan (kumare3)
03/31/2023, 5:23 AM
No our goal is keep complete parity between flytekit and backend (all backend though is one unit) across a major version
y
Yubo Wang
04/03/2023, 10:52 PM
(all backend though is one unit) so how do Flyte team keep versions consistent across propeller and admin? through helm charts?
k
Ketan (kumare3)
04/04/2023, 12:10 AM
yes, but also uses grpc
we make sure we do not break
but we do not test across a large versionset
2 Views
#ask-the-community
Join Slack