Daniela Plascencia

Hi folks, here's a list of issues we have run into (charmed kubeflow). * kubeflow/pipelines#7196, canonical/kfp-operators#54 - might get fixed by kubeflow/pipelines#7351 * kubeflow/kubeflow#6056, canonical/bundle-kubeflow#460 - might get fixed by...

@johnugeorge @tenzen-y thanks for the explanation. In my case, adding `metricsCollectorSpec:` to the [grid example](https://raw.githubusercontent.com/kubeflow/katib/master/examples/v1beta1/hp-tuning/grid.yaml) solved the issue. I am able to click the Trials/YAML/Details tabs in the Experiment view...

@johnugeorge My [webhook](https://hastebin.com/anivaluneq.yaml) is in the cluster, though I am not sure if there is a misconfiguration.

@johnugeorge my trials' `metricsCollector` is empty, I will check the webhook and try to see what might gone wrong. ```yaml spec: metricsCollector: {} ```

I was able to fix my issue, though I discovered mine was different than @ccastro-pedro, as I was not getting the sidecar metrics container injected in the trials pods due...

Hi @natalian98, thanks for filing canonical/training-operator#44 and proposing a fix for it here. I think that we probably want to move away from `patch` and `create` and instead use `apply`...

Thanks @ca-scribner, LGTM. Your branch seems to have conflicts, do you mind resolving them so we can merge?

Hi @hazem-soussi, the error message you are getting (`subprocess.CalledProcessError: Command '['./istioctl', 'install', '-y', '-s', 'profile=minimal', '-s', 'values.global.istioNamespace=metallb-system']' returned non-zero exit status 1.`) is usually caused by the `istio-pilot` charm not...

Thanks for looking into it @NohaIhab ! I think the approach is right, we need to decrease the `root-reserve-mb` number to fit the new storage size. Let's do a cannon...

hey @thesuperzapper, just to check for updates on this, when can we cut the new patch release? We'd like to work on the patch release next week.