<@U06RKAMK0UC> Does flytekit version need to match...
# ask-ai
w
@ancient-wolf-19325 Does flytekit version need to match the flyte core helm chart version?
j
Reasoning Complete! 🤖 🔍 Searched knowledge base: I'll look up official documentation to see if flytekit and Flyte core versions need to match, or if there are compatibility guidelines. • Searching over 10 data sources from the following: File, Github File, Github Issue, Web • Found 49 documents that could be relevant from the following data sources: Github File, Github Issue, Github Pull Request. • Filtered down to the top 30 most relevant documents. ✍️ Generated answer: Based on the documentation, Flytekit and Flyte core (Helm chart) versions do not need to match exactly, but it's best to keep their major/minor versions aligned for compatibility. You can upgrade them independently, but always check release notes for any breaking changes.
No, the
flytekit
version does not need to exactly match the Flyte core Helm chart version. While it is recommended to keep
flytekit
and Flyte core components (deployed via Helm) reasonably aligned for best compatibility, they are versioned and released independently. The Flyte release process aligns versions for user-facing components (like Flytekit, FlyteAdmin, FlytePropeller, Console, etc.), but you can upgrade
flytekit
separately as needed, and the Helm chart version may differ [release cycle process updates]. However, using very old or very new versions of
flytekit
with mismatched Flyte core may lead to incompatibilities or missing features, so it's best practice to use versions from the same release cycle or check the release notes for compatibility guidance [release cycle process updates]. Would you like more detail on how to check for compatibility or manage upgrades? Sources: - release cycle process updates 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.