<!here>, we have included an important security fix in the flyte v1.1.0 release. We highly encourage everyone to upgrade. A CVE will be released on July 12th that will include more information about the vulnerability. If you have specific questions, please don’t hesitate to DM me until then.

are the docker images for flyteadmin/propeller/scheduler/console tagged as latest fine? there are some newer ones, eg. flytepropeller has v1.1.15-patch1 but v1.1.14 is marked as latest, wondering which to use

I would encourage you to pick the ones tagged with the flyte release since that’s where most of the testing/validation happens. e.g. (

flyteadmin-release:v1.1.0

)

Also, what is the best way to upgrade the version? I did download latest helm values but doing

helm template

, looks like the templates are still pointing to

v1.0.2

@Yuvraj, Can you take a look at this?

Yes

you can set the image in the values yaml, eg.

flytescheduler:
  image:
    tag: v1.1.0
    repository: <http://cr.flyte.org/flyteorg/flytescheduler-release|cr.flyte.org/flyteorg/flytescheduler-release>
    pullPolicy: IfNotPresent

then doing helm upgrade worked fine for me

@Shahwar Saleem You can also use helm registry

helm repo add flyteorg <https://helm.flyte.org>
helm repo update
helm upgrade -n flyte --create-namespace flyte flyteorg/flyte-core -f <https://raw.githubusercontent.com/flyteorg/flyte/master/charts/flyte-core/values-eks.yaml> -f values-override.yaml --install (It wll install the latest helm release)

Thanks @Yuvraj I can see latest images in templates now!