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
Each charm has a set of manifest files that have to be upgraded to their target version. The process of upgrading manifest files usually means going to the component’s upstream repository, comparing the charm’s manifest against the one in the repository and adding the missing bits in the charm’s manifest
The only change that was introduced in kfp manifests between 1.9.0-rc.0 and 1.9.0 release is the following to resolve kubeflow/manifests#2794. However, our KFP Pods don't have an istio sidecar, thus we don't need any AuthorizationPolicy to configure these pods. Thus, we don't need to bring any changes to kfp.
Context
Each charm has a set of manifest files that have to be upgraded to their target version. The process of upgrading manifest files usually means going to the component’s upstream repository, comparing the charm’s manifest against the one in the repository and adding the missing bits in the charm’s manifest
What needs to get done
See the release handbook
Definition of Done
Manifests and images are updated to the corresponding version for 1.9.0
The text was updated successfully, but these errors were encountered: