What is the preferred way to deploy these days? We...
# flyte-deployment
t
What is the preferred way to deploy these days? We have been happily using Flyte for a year now but the setup has changed significantly compared to back then and updating to 1.6 is not straightforward. Should we consider the manifests from the recent release as the most authoritative or instead the helm-chart approach from this guide which btw seems to be installing an entirely new application
flyte-binary
that seems to bundle ... well everything? Do you recommend using flyte-binary these days unless one is using a multi-cluster setup?
j
if you’ve already been using flyte with separate deployments for admin, propeller, datacatalog and console, the flyte-core chart might be a better fit for you. flyte-binary was a way help new users onboard faster basically.
t
Thanks for the direction!
I noticed that the flyte-core chart is using the by now somewhat outdated k8s apis
<http://apiextensions.k8s.io/v1beta1|apiextensions.k8s.io/v1beta1>
and
<http://networking.k8s.io/v1beta1|networking.k8s.io/v1beta1>
are there any newer versions of the chart?
j
@Tim Bauer do you have a link for the above?
t
Difficult to link the chart but if you run
Copy code
helm template flyte-backend flyteorg/flyte-core --namespace flyte | grep apiextensions
You will see that its using the old v1beta1 api.
j
We should be able to just dynamically derive api versions based on the cluster version
t
Ah maybe I'm just too bad at using helm - our approach is basically to not use it but render manifests from it using
template
and than overlaying our kustomizations.
you have to provide it some information to render the correct values here
t
Ah its much smarter than I knew.
j
there should be a CLI arg to provide the api versions
first arg
t
Awesome, thank you!
159 Views