You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've installed the flyte-core helm chart in version 1.0.2 on one of our clusters yesterday, and it came up successfully. Whilst trying to upgrade another cluster today, we did get an ImagePullBackoff when trying to pull cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2.
I can also confirm not being able to pull that image locally:
❯ docker pull cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2
Error response from daemon: manifest unknown
Has anything changed here recently?
Expected behavior
NA
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
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.
Describe the bug
We've installed the flyte-core helm chart in version 1.0.2 on one of our clusters yesterday, and it came up successfully. Whilst trying to upgrade another cluster today, we did get an ImagePullBackoff when trying to pull cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2.
I can also confirm not being able to pull that image locally:
Has anything changed here recently?
Expected behavior
NA
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: