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
{{ message }}
This repository has been archived by the owner on May 3, 2022. It is now read-only.
A chart version resolve problem must be surfaced and visible to end users.
Example of the problem:
E0829 12:28:51.316030 4651 application_controller.go:170] error syncing Application "olegs-test/testapp-v1alpha1" (
will retry: true): failed to resolve chart version [name: "nginx", version: "1.0.2", repo: "http://0.0.0.0:8879"]: no
chart version found
@Shubhamchinda hey, howdy! It seems this issue is planned to end up in 0.6 and the first release of this branch is now scheduled on Sep 16. Do you think there is a chance you can finish this task until this moment? Thanks!
This change forces application controller to report chart version
resolution issues in application conditions. This provides some
transparency over this process.
Signed-off-by: Oleg Sidorov <[email protected]>
A chart version resolve problem must be surfaced and visible to end users.
Example of the problem:
Application object:
Expected behavior: Application object contains some hints about the problem.
The text was updated successfully, but these errors were encountered: