[07:44:07] 10serviceops, 10Prod-Kubernetes, 10SRE, 10Kubernetes, and 2 others: Upgrade Calico - https://phabricator.wikimedia.org/T207804 (10JMeybohm) [07:44:34] 10serviceops, 10Prod-Kubernetes, 10SRE, 10Kubernetes: Set resource requests and limits for calico PODs - https://phabricator.wikimedia.org/T277877 (10JMeybohm) 05Open→03Resolved Calico components are running with resource definitions in all clusters now. [12:43:17] 10serviceops, 10Add-Link, 10Data-Persistence (Consultation), 10Growth-Team (Current Sprint), 10Patch-For-Review: Determine why service responses are slow and what we can do about it - https://phabricator.wikimedia.org/T279411 (10kostajh) @akosiaris We seem to have gone over the max memory usage limit aga... [13:52:17] 10serviceops, 10Add-Link, 10Data-Persistence (Consultation), 10Growth-Team (Current Sprint), 10Patch-For-Review: Determine why service responses are slow and what we can do about it - https://phabricator.wikimedia.org/T279411 (10akosiaris) >>! In T279411#7081801, @kostajh wrote: > @akosiaris We seem to h... [14:00:36] 10serviceops, 10Add-Link, 10Data-Persistence (Consultation), 10Growth-Team (Current Sprint), 10Patch-For-Review: Determine why service responses are slow and what we can do about it - https://phabricator.wikimedia.org/T279411 (10kostajh) >>! In T279411#7081972, @akosiaris wrote: >>>! In T279411#7081801,... [14:17:59] 10serviceops, 10Add-Link, 10Data-Persistence (Consultation), 10Growth-Team (Current Sprint), 10Patch-For-Review: Determine why service responses are slow and what we can do about it - https://phabricator.wikimedia.org/T279411 (10akosiaris) >>! In T279411#7082010, @kostajh wrote: >>>! In T279411#7081972,... [15:21:24] jayme / akosiaris should we discuss this again on monday? [15:21:36] even tomorrow [15:21:44] I'm out till monday [15:21:51] ah, cool. Monday it is then [15:22:43] ok I'll add a meeting [15:23:09] <_joe_> discuss what? [15:23:11] Are there any concerns around bumping the (non-future) envoy package and image or is everything that uses it pinned? [15:23:35] <_joe_> hnowlan: physical hosts will require an actual deployment [15:23:52] <_joe_> and kubernetes deployments will need a change of the global config with the image version pinned [15:24:29] _joe_: about deploying apache flink [15:25:05] effie: can I lurk in meeting? :) [15:25:49] only if you can help us find a solution [15:26:09] :D [15:26:32] ottomata: what time is the earliest for you in UTC ? [15:27:03] <_joe_> the only real solution is to realize there is no spoon [15:28:28] hm, usually 1pm UTC, but don't adjust meeting time for me, just make it and add me as optional and i'll make it if i can [15:28:53] effie: i'm hoping to help make using stream processing in prod easier as part of event platform work next FY [15:29:47] that will probably work no worries [15:30:09] which mostly includes the operationalizing work you are doing now, so i'd like to keep my eyeballs on it :p [15:32:18] <_joe_> ottomata: or go back to the drawing board and think of a different architecture if flink proves brittle/hard to maintain [15:32:39] <_joe_> like, I would like y'all to consider workflows based on things like kubeless/knative [15:33:43] <_joe_> flink seems like an aircraft carrier we want to use not just for tactical advantage but also as a cruiseship to me. It will make do, but I'm not sure it's the one-size-fits-all solution [15:34:34] _joe_: +1 [16:03:15] _joe_: I'm curious about flink especially for its connector support. i'm intersted in making the data integration bits easier. consume, reshape it, store it somewhere for serving [16:03:52] https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/connectors/datastream/overview/ [16:32:21] I'll be out till monday, have a nice rest of the week and weekend you all o/ [16:36:28] cheers