Ensure charmhub tracks and charms are up to date for CKF 1.10

[orfeas-k]

Context

Ensure that charmhub tracks for new charm versions are available and new charms belong to the Kubeflow Charmers.

What needs to get done

^^

Definition of Done

Above is done.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6609.

This message was autogenerated

[orfeas-k]

Created tracks according to this issue kubeflow/community#767. For charms that are not there, I followed issues linked in kubeflow/community#768 and created the following:

• katib tracks 0.18 according to AutoML WG roadmap for KF 1.10 kubeflow/community#772
• kfp and envoy tracks 2.4 according to Pipelines WG roadmap for KF 1.10 kubeflow/community#771
• kserve track 0.14 according to KServe roadmap for KF 1.10 kubeflow/community#775
• training track 1.9 according to [Release] Training Operator 1.9 Roadmap kubeflow/training-operator#2169

Note that for argo, we 're already using 3.4 as mentioned in the first issue. WRT KFP 2.4, although not released yet, main uses argo 3.4.17 and they 're not planning to bump this version (see 2.4 milestone https://github.com/kubeflow/pipelines/milestone/12). Thus, 3.4.17 will be used for 1.10. Thus, my understanding is that we don't need a new track for argo-controller. We can backport changes to 3.4 and refresh the charm.

For the charm that are now being developped, I created those two tasks and added them to the corresponding epics:

• Transfer ownership to kubeflow-charmers and create needed tracks github-profiles-automator#16 (closed as a duplicate of the below since we 're creating a python library and one charm after all)
• github profiles IR charm: Transfer ownership to kubeflow-charmers and create needed tracks #1186

[NohaIhab]

thanks for the nice summary @orfeas-k !
LGTM