Andrew Scribner

@zachomedia mentioned getting all images in use from pods would be preferable to nodes because we may start using virtual node pools Sprint discussion raised that we'll be moving to...

I've tried for 30 minutes to write this comment and can't articulate it very well... :| I'm having trouble picturing a workflow that: * Automatically migrates any user's vulnerable notebook...

Yeah this is really tough as it is so situational. We want users to be without interruption, but we also don't want to keep near-empty nodes going, etc... And then...

@alexlatchford I have had similar results with experiments in users setting their own timeouts :) I'm curious what are the negative effects of notebook pod disruption that people are reporting...

This looks really promising! I wonder how this interacts/overlaps with kubeflow pipelines, but in general this looks really nice and the demo was excellent. I'd love to contribute to the...

For anyone coming here and wanting a tl/dr on the issue search (some of this is a repeat of @Bobgy's great summary above): * [Early implementation tracking issue](https://github.com/kubeflow/pipelines/issues/1223): Includes a...

Oh great! so something like the api behind [this call](https://github.com/kubeflow/pipelines/blob/14017cced610eb289eaaba858df1183d168549ef/sdk/python/kfp/_client.py#L1299) does have the ability to accept namespace once things are regenerated?

Clarifying one thing, by default Istio's `Gateway` objects do work across namespaces (`Gateway` in `namespace-1` can refer by selector to a deployment of `image: istio/proxy` in `namespace-2`), so the `Gateway`...

After some more tweaking, I found that setting: ``` local-gateway.knative-serving.knative-local-gateway: "knative-local-gateway.namespace-1.svc.cluster.local" ``` resulted in: * creation of `gateway/knative-ingress-gateway` and `gateway/knative-local-gateway`. These seem to always be created, regardless of whether they're...

I am also confused. Why argo-controller/0 went into error is one question (don't see anything in the debug-logs that tell me), but that argo-controller/1 was prevented from taking over sounds...