2025-02-01 12:14:58 <nu__> oof
2025-02-01 12:16:59 <nu__> ill check
2025-02-01 12:18:54 <ikke> nu__: would be appreciated
2025-02-01 12:19:07 <ikke> I tried to work around it with a wg tunnel, but did not really succeed
2025-02-01 12:29:24 <nu__> im on fosdem but don't have much to do anyways
2025-02-01 13:56:20 <nu__> i can repro it
2025-02-01 14:54:18 <nu__> could you set the mtu to 1384 ?
2025-02-01 14:56:07 <nu__> im announcing it via RA-s but linuxes dont seem to care about it
2025-02-01 15:23:31 <ikke> let me try
2025-02-01 15:25:54 <ikke> It seems to work, but I apparently have to set it on each container interface
2025-02-01 16:05:11 <nu__> hmm
2025-02-01 16:05:26 <ikke> I'm adding it to the default lxc config now
2025-02-01 16:05:57 <nu__> i wonder why is this broken by default with wireguard
2025-02-01 16:06:14 <ikke> Good question
2025-02-01 16:08:30 <ikke> Let's see if that makes prowlar build now
2025-02-01 16:09:46 <nu__> im kind of clueless when it comes to MTU
2025-02-01 16:10:05 <nu__> i need to find a way to make this works without mods
2025-02-01 16:10:53 <ikke> Normally https://en.wikipedia.org/wiki/Path_MTU_Discovery should take care of it
2025-02-01 16:11:27 <ikke> It relies on 'packet too big' / 'fragmentation needed' icmp packets
2025-02-01 16:12:44 <ikke> So if those packets for some reason are not able to make it back, pmtu discovery is broken
2025-02-01 16:13:44 <ikke> aarch64 was now able to build prowlarr
2025-02-01 16:13:47 <ikke> \o/
2025-02-01 16:23:30 <nu__> \o/!
2025-02-02 14:08:41 <nu__> something is up with natting:/ ill implement the final networking next week
2025-02-02 14:09:26 <ikke> Thanks
2025-02-04 19:47:50 <zv> re. the equinix stuff, come talk to us (adelie) about hardware and possible partnerships for either colo, managed, or VM or other resources.
2025-02-04 19:49:24 <zv> not going to chase anyone down about it but thought i'd offer a reminder. PM me or email about it (me^zv.io)
2025-02-04 20:18:34 <ikke> zv: thanks, we have received quite a number of offers already, but we'll keep this in mind as well (especially for our long-term goal)
2025-02-04 21:17:33 <zv> sounds good. for reference, we self host everything
2025-02-04 21:18:24 <ikke> zv: you mean like paying for your own infra?
2025-02-04 21:19:50 <zv> yes. like, donations pay for data center space and occasionally hardware. we run it all.
2025-02-04 21:20:17 <ikke> Right, that's nice
2025-02-04 21:21:52 <zv> equinix f'd us a while back, too, and that is part of the reason we opted to be in total control of our hardware
2025-02-04 21:22:11 <zv> (aside from it being more affordable than renting, if not sponsored)
2025-02-05 02:47:37 <pj> https://lobste.rs/s/gjdafu/seeking_support_after_equinix_metal
2025-02-06 16:28:08 <ikke> clandmeter: ^
2025-02-06 16:53:51 <night> meow
2025-02-06 16:54:02 <night> o/ - I hear that Alpine was looking for colocation space etc?
2025-02-06 16:55:27 <ikke> night: yes, though we have already received quite a number of offers, which we are sitting through 
2025-02-06 16:57:26 <night> ah i see, would it still be helpful to offer anything?
2025-02-06 17:14:55 <ikke> night: depends on what you have to offer
2025-02-06 17:15:17 <ikke> But we already see some very attractive offers
2025-02-06 17:26:31 <night> ikke:  we can offer essentially everything being asked for on the list on a no-attribution basis (we don't ask to be placed on your sponsors list or anything) 
2025-02-06 17:26:54 <night> we have sites in Amsterdam (NL), Dronten (NL), San Jose, Seattle,  New York; network ports are all 2x25GE
2025-02-06 17:27:01 <night> we can probably acquire whatever hardware you need 
2025-02-06 17:27:40 <ikke> Then please do send an email to infra@a.o
2025-02-06 17:28:02 <night> i was curious how strong of an ask the Amsterdam/NL requirement was?
2025-02-06 17:29:14 <night> we have 50-70kW free in our seattle site, which we mostly use to house OSS projects atm
2025-02-06 17:40:03 <ikke> night: that's mostly for just colocation 
2025-02-06 17:40:14 <ikke> If we have to install hardware ourselves 
2025-02-06 17:40:21 <night> if we managed the entire thing, is seattle ok?
2025-02-06 17:40:42 <night> er, hardware racking/etc wise
2025-02-06 17:41:21 <ikke> Yes
2025-02-06 18:25:12 <night> ikke: cool; sent off an email.
2025-02-06 18:25:19 <ikke> Thanks
2025-02-06 18:36:23 <clandmeter> ikke: ?
2025-02-06 18:42:42 <ikke> gbr2-dev1 disk is almost full, could you check?
2025-02-06 20:01:40 <clandmeter> ikke: how can i see what is taking al the space?
2025-02-06 20:01:57 <clandmeter> could it be docker using too much log spoace?
2025-02-06 20:03:23 <ikke> gdu /
2025-02-06 20:03:40 <clandmeter> im running prune first
2025-02-06 20:04:45 <clandmeter> hmm
2025-02-06 20:04:52 <clandmeter> edge db is taking 16G
2025-02-06 20:05:00 <clandmeter> i wonder if thats normal
2025-02-06 20:05:46 <clandmeter> looks like it is
2025-02-06 20:13:31 <clandmeter> ikke: its partially renovate cache
2025-02-06 20:13:43 <clandmeter> appstteam also takes 5gb
2025-02-06 20:21:30 <ikke> You could purge the renovate cache
2025-02-07 13:06:21 <nekocentral> Saw the blog post, I got a machine mostly running idle and a spare IP and am Willing to give yall some VM´s to run the CI
2025-02-07 14:27:34 <ikke> nekocentral: thanks, do we do have a lot of offers already 
2025-02-07 15:59:36 <nekocentral> Good to hear haha
2025-02-07 17:31:50 <mio> is pkgs-old.a.o still available or has it been retired?
2025-02-07 17:32:41 <mio> it's returning "404 page not found" at my end
2025-02-07 18:39:35 <clandmeter> What is wrong with the new one
2025-02-07 18:44:06 <mio> nothing's wrong, it's good ... just 1-2 minor things about the old one that made it more convenient to use? e.g. linking to git.a.o for the repository to see the APKBUILD/history instead of gitlab (which seems to bave trouble showing history for certain aports with long history)
2025-02-07 18:44:24 <mio> and liked the way the old flagged list was sorted
2025-02-07 18:45:25 <mio> and admittedly have occasionally used the manual flagging
2025-02-07 18:45:59 <mio> while anitya information gradually improves
2025-02-07 18:49:11 <mio> do like the new one includes info for loongarch64, was using both
2025-02-07 19:08:26 <fossdd[m]> yeah the sorting of the flagged list is certainly a good point
2025-02-07 19:21:32 <mio> :)
2025-02-07 19:38:47 <clandmeter> mio: i turned it off as i thought nobody would use it
2025-02-07 19:38:54 <clandmeter> i can turn it back on again
2025-02-07 19:39:10 <clandmeter> but better if we fix things in new one
2025-02-07 19:39:38 <clandmeter> fossdd[m]: you want to be added as maintainer to pkgs?
2025-02-07 19:40:38 <mio> clandmeter: that would be good in the meantime, thanks. and agreed :)
2025-02-07 19:58:06 <clandmeter> mio: would you be able to generate a patch to implement the old behaviour? 
2025-02-07 19:58:21 <clandmeter> put it under flagging or flagged
2025-02-07 19:58:35 <clandmeter> just need to find a place to put the message we have no
2025-02-07 19:58:35 <clandmeter> w
2025-02-07 20:07:19 <mio> clandmeter: you mean for sorting the flagged list?
2025-02-07 20:08:37 <clandmeter> or have the flagged in a separate page like before
2025-02-07 20:08:42 <clandmeter> sorted or whatever
2025-02-07 20:11:18 <mio> not sure, can try looking into it. currently the flagged list sorts by build date, if the db stores anitya flag date then maybe a sort based on it would be good
2025-02-07 20:40:24 <fossdd[m]> <clandmeter> "fossdd: you want to be added..." <- sure, wouldnt certainly mind :)
2025-02-08 17:12:02 <fossdd[m]> clandmeter: is it correct that i cant push to apkbrowser's master?
2025-02-08 17:17:57 <ikke> fossdd[m]: you cannot directly push to protected branches
2025-02-08 17:18:06 <fossdd[m]> ah
2025-02-08 17:19:38 <ikke> fossdd[m]: and as it's setup now, you can also not merge anything
2025-02-08 17:19:43 <ikke> into master
2025-02-08 19:15:47 <clandmeter> ikke: Can you adjust it?
2025-02-08 19:16:08 <clandmeter>  Not sure what I need to do
2025-02-08 19:16:19 <ikke> That fossdd[m] can merge?
2025-02-08 19:16:36 <ikke> I can do something, but that would count for all developers
2025-02-08 19:16:54 <ikke> Don't think that's a problem
2025-02-08 22:00:29 <clandmeter> fossdd[m]: ikke has fixed it so you can merge things via MR
2025-02-10 14:21:43 <ncopa> im struggling a bit with my alpinelinux.org email from macOS. It works on alpine, but right now then wifi network does not work when I reboot to alpine. It worked the other day. would be nice if I could get the email working from macOS though.
2025-02-10 14:24:09 <ikke> What issues do you have?
2025-02-10 14:32:17 <ncopa> i have not been able to send via smtp.a.o
2025-02-10 14:32:45 <ncopa> but it appears to have been just me who am not able to manage my passwords
2025-02-10 14:33:20 <ncopa> yeah, it went thought now
2025-02-10 16:06:31 <ikke> 👍
2025-02-10 19:38:21 <ikke> blaboon: Any idea why Alpine 3.21 is not yet available as image?
2025-02-10 19:45:21 <blaboon> we've had builds going for it since it launched, but some recent organizational changes within akamai have been dramatically slowing down the speed at which we can launch new distros unfortunately, so it may take some time still. we're trying to get the necessary PRs through as fast as we can
2025-02-10 19:45:51 <ikke> blaboon: alright, thanks
2025-02-10 19:49:43 <blaboon> it's been getting extra bad in recent months, so we're taking some steps to move everything distro-related into repos that we on the distro team control so that we're no longer bound by other team's release windows. that will put us back to same-day releases like how we used to be able to do, but will also take some time to get there
2025-02-10 19:50:43 <blaboon> unrelated, but i also renewed the sponshorship for your account by another year last week :)
2025-02-10 19:51:03 <ikke> blaboon: aha thanks for that, I was already wondering whern that would come up again
2025-02-10 19:51:25 <ikke> We really appreciate the sponsorship
2025-02-10 19:51:55 <ikke> blaboon: I hope you'll manage that :)
2025-02-10 19:52:16 <ikke> 
ACTION suspects monorepos

2025-02-13 01:54:55 <trycatch> Infra team still looking for sponsors for mirror servers due to the Eqx Metal sunset?
2025-02-13 04:16:05 <ikke> trycatch: we have received quite a number of responses, which we're going through. If you could offer something with enough storage in a less common location we're still interested.
2025-02-13 04:49:33 <trycatch> Could over Singapore, Sydney and LA. Would be dedicated hardware on a global anycast network
2025-02-13 05:02:31 <ikke> trycatch: please send an email to infra@alpinelinux.org
2025-02-13 23:46:13 <sertonix[m]> Someone has reported bein falsely blocked from the wiki https://gitlab.alpinelinux.org/alpine/help/-/issues/41
2025-02-14 00:20:59 <ncopa> not sure how to deal with that
2025-02-14 00:21:18 <ncopa> the upload from arm build server is painfully slow
2025-02-14 00:21:27 <ncopa> may not be able to do docker releases due to that
2025-02-14 00:22:18 <ncopa> like 100kb/s
2025-02-14 04:41:15 <iggy> 172.16 is a private IP space? Shouldn't the block be on the X-Forwarded-For instead of the reverse proxy IP?
2025-02-14 08:03:43 <nu__> ncopa, sorry it should be solved now
2025-02-14 08:04:35 <nu__> in 2 days it will get back it's dedicated 1 gig link
2025-02-14 08:32:33 <trycatch> ikke, sent
2025-02-14 08:33:45 <ikke> Thanks, we received it
2025-02-14 09:56:22 <clandmeter> yes in my promotional email tab :)
2025-02-14 11:12:07 <ncopa> nu__: no worries, it just took a bit time, but its done now. releases are out
2025-02-14 11:12:18 <ncopa> wanted to get the releases out before weekend
2025-02-14 11:13:06 <ncopa> and today im gonna spend on the the beach
2025-02-14 11:14:46 <ncopa> ikke: do you think you could post an email to announce mailing list? with a link to https://alpinelinux.org/posts/Alpine-3.18.12-3.19.7-3.20.6-3.21.3-released.html
2025-02-14 14:15:55 <vkrishn> setup-alpine currently only handles fastest mirror and not geo-wise?
2025-02-14 14:16:35 <vkrishn> is someone working on geo part or some suggested code i can look at
2025-02-14 14:17:35 <vkrishn> why no mirrors in india?
2025-02-14 14:19:47 <vkrishn> country is not helpful?
2025-02-14 14:21:02 <ikke> vkrishn: no one offered one
2025-02-14 14:22:48 <vkrishn> such a shame
2025-02-14 14:25:43 <vkrishn> i am thinking/toying to add geo part in that code, might need to add improve mirrors.json or add mirrors.geo.json, hope that would be ok if accepted
2025-02-14 14:27:00 <vkrishn> nginx has geoip mod, might toy with it
2025-02-14 14:28:15 <vkrishn> mirrors.a.o is handled by nginx at front(proxy)?
2025-02-14 14:28:32 <ikke> The json file is generated 
2025-02-14 14:28:54 <vkrishn> hm, ok, point me to code pls
2025-02-14 20:15:55 <ikke> ncopa: done
2025-02-14 21:47:16 <ncopa> Thank you!
2025-02-15 18:20:33 <ikke> nu__: fyi, tomorrow I'll be occupied most of the day, I'll be available again in the evening
2025-02-15 19:49:11 <nu__> ikke: it should be up now
2025-02-15 22:54:32 <ptrc> not sure if it's an issue with alpine gitlab being slow or just gitlab in general, but i've just encountered a delay between pushing a branch and gitlab allowing me to open a MR for it; it otherwise thought that the branch doesn't exist, and needed a minute to realize it does
2025-02-16 19:33:18 <durrendal> ikke: I know you have a lot going on right now migrating servers, so there is absolutely no need to look at this right now, but I have that openbao container in a state where it could be tested. I don't have permissions to push it to infra/docker so it's currently here: https://gitlab.alpinelinux.org/durrendal/openbao
2025-02-19 07:13:44 <clandmeter> durrendal: looks nice
2025-02-19 07:14:29 <clandmeter> durrendal: i think we may want to have another infra meeting soonish, ones we cover the sponsor management part. 
2025-02-19 13:46:30 <durrendal> clandmeter: thanks! It took a bit to put together, but January's are always super busy for me. 
2025-02-19 13:47:34 <durrendal> clandmeter: another infra meeting sounds like a good plan, just let me know once your time frees up. 
2025-02-19 13:48:14 <durrendal> I can only imagine you have your hands full with the flood of outreach we got after the request for sponsorship post
2025-02-20 12:31:08 <fossdd[m]> huh all CI jobs are stuck now since the x86_64 CI is offline
2025-02-20 12:32:10 <ikke> yes
2025-02-20 16:44:28 <ikke> fossdd[m]: I've adjusted the tags of the job so that it can run on other runners as well, so new / rebased MRs should at least build other jobs now
2025-02-20 16:45:38 <fossdd[m]> yes saw that thanks!
2025-02-21 11:46:03 <qaqland> cgit got 502
2025-02-21 11:52:16 <ikke> AI crawlers
2025-02-21 14:56:01 <clandmeter> Test
2025-02-21 14:56:09 <mikemrm[m]> 👋 howdy!
2025-02-21 14:56:13 <ikke> hello
2025-02-21 14:56:13 <clandmeter> Hi mikemrm[m] 
2025-02-21 14:56:31 <clandmeter> ikke please sync
2025-02-21 14:56:42 <clandmeter> he is man :)
2025-02-21 14:56:46 <clandmeter> our
2025-02-21 14:56:54 <ikke> :)
2025-02-21 14:57:06 <ikke> server is booting at the moment
2025-02-21 14:57:10 <mikemrm[m]> heh. provisioning now, should show as alpine os
2025-02-21 15:00:56 <ikke> cool, I'm in now
2025-02-21 15:01:11 <ikke> is it expected that the sos console does not take any input?
2025-02-21 15:01:17 <ikke> oh, now it does
2025-02-21 15:01:28 <ikke> mikemrm[m]: thanks!
2025-02-21 15:02:24 <mikemrm[m]> awesome! looks like it all came up fine.
2025-02-21 15:03:35 <mikemrm[m]> might need to disconnect and reconnect. sos disables input during deprovision step. so if you've been on it for a while it might still be in that state
2025-02-21 15:04:08 <mikemrm[m]> you bet!
2025-02-21 15:10:51 <clandmeter> Thanks Mike 
2025-02-21 15:13:06 <ikke> Ok, we have CI again
2025-02-21 15:13:08 <ikke> for x86_64
2025-02-21 15:13:58 <mio> \o/ thanks!
2025-02-21 15:15:00 <clandmeter> Sounds handy
2025-02-21 15:18:31 <ikke> rather convenient
2025-02-21 15:49:49 <durrendal> Excellent news!
2025-02-21 16:15:53 <fossdd[m]> \o/ thank you very much!
2025-02-21 19:58:55 <funderscore> \o/
2025-02-22 11:13:31 <pj> Matrix Foundation is going to shutdown bridges because they have no money (they expect $100K until march to extend the service and $600K to keep it going at all)
2025-02-22 17:16:10 <funderscore> pj great
2025-02-22 17:16:24 <funderscore> :/
2025-02-22 17:19:38 <panekj> seems it's 29k until reaching the goal of 100k
2025-02-22 17:19:55 <panekj> so it will run at least a month longer
2025-02-22 17:27:04 <funderscore> good
2025-02-22 17:27:13 <funderscore> well.. "run"..
2025-02-22 17:27:25 <funderscore> Not like it's maintained much anyway.
2025-02-22 17:27:52 <funderscore> panekj: where did you get that number from though, if I may ask?
2025-02-22 17:28:06 <panekj> their donation apge
2025-02-22 17:28:27 <funderscore> this? https://donorbox.org/keep-matrix-exciting
2025-02-22 17:28:39 <panekj> yes
2025-02-23 08:29:46 <clandmeter> For what do they need that much of 💰 just to run a bridge?
2025-02-23 08:31:05 <clandmeter> https://matrix.org/blog/2025/02/crossroads/
2025-02-23 09:18:16 <ikke> restarting it
2025-02-23 11:02:20 <f_> clandmeter: and also to barely maintain them
2025-02-23 11:04:49 <f_> https://github.com/matrix-org/matrix-spec/issues/571#issuecomment-2673151460
2025-02-23 11:05:32 <f_> 
ACTION doesn't think shutting down bridges will make the foundation much profitable

2025-02-23 13:44:08 <pj> it's a big chunk but seems disingenuous comparing it to their expenses
2025-02-23 18:26:06 <f_> pj: yes, that's what I mean, it's nothing compared to the rest
2025-02-23 18:26:39 <f_> Arguably running the matrix.org homeserver aught to take much, much more resources and $$$, for instance.
2025-02-23 18:28:01 <f_> As of now the bridges mostly only get secfixes and fixes when there's a breaking change on the matrix protocol
2025-02-23 20:24:33 <clandmeter> everything wrong with matrix is perfectly outlined in their blog post. 
2025-02-24 01:00:59 <iggy> call me crazy, but I won't miss the irc bridges
2025-02-24 01:37:42 <peterson[m]> From Trusted and Vouched Dealers... (full message at <https://matrix.org/oftc/media/v1/media/download/AU3bC7goD7mN_5PMfLkvP_spMVxsm8RDlfJ3JTrdHvtk5nJlZs-LDiADYPEzCTGNu5EPjOl4UFV5vj8HiwRTRulCeVfbNgjgAG1hdHJpeC5vcmcvT3plRUF2dXFwaWF6WG9hQWd3eUpCVkxH>)
2025-02-24 01:40:09 <pj> can I get op to ban the user
2025-02-24 01:40:48 <pj> and in #alpine-offtopic 
2025-02-24 01:42:29 <pj> cc: ikke clandmeter
2025-02-24 01:47:25 <pj> maybe when matrix kills off the bridges, we will have peace finally
2025-02-24 06:16:28 <fabricionaweb> I wouldn't miss it 
2025-02-24 09:38:50 <f_> same
2025-02-24 09:40:52 <f_> At least for IRC-first channels
2025-02-24 15:20:04 <ikke> ..
2025-02-24 15:23:15 <clandmeter> whats wrong with it?
2025-02-24 15:24:12 <clandmeter> ikke: seems i cannot ssh to it?
2025-02-24 15:24:22 <ikke> Into what?
2025-02-24 15:24:28 <clandmeter> the server
2025-02-24 15:24:34 <clandmeter> of tpaste.us
2025-02-24 15:24:47 <clandmeter> did it have a ssh upgrade?
2025-02-24 15:34:55 <clandmeter> that box is not healty
2025-02-24 15:34:59 <ikke> Not that I'm aware of
2025-02-24 15:35:36 <clandmeter> ash: cant fork resource not available
2025-02-24 15:35:39 <clandmeter> when you run ls
2025-02-24 15:36:19 <clandmeter> rebooting it
2025-02-24 15:36:23 <clandmeter> but i guess it will rail
2025-02-24 15:36:27 <clandmeter> fail
2025-02-24 15:36:38 <ikke> Yeah, htop fails as well
2025-02-25 18:06:55 <invoked> fyi based on conversation in #oftc, #debian-social is going to run their own matrix oftc irc bridge, tor project might go in on that with them
2025-02-25 18:10:44 <invoked> also appservice-irc is being archived on github (it's not clear to me if that's tied into the $100k funding)
2025-02-25 18:11:21 <pj> pretty sure they want to get rid off maintaining both the code and bridges
2025-02-25 18:11:27 <pj> no matter if they have money
2025-02-25 18:11:59 <invoked> it's a nice round number, isn't it
2025-02-25 18:12:07 <invoked> almost seems... arbitrary
2025-02-25 18:12:37 <pj> the full goal is 610k
2025-02-25 18:12:45 <pj> and that's way too much for just bridges and ops
2025-02-25 18:12:51 <invoked> agreed
2025-02-25 18:39:22 <f_> invoked: debian-social already runs their own matrix oftc irc bridge
2025-02-25 18:39:27 <f_> for a long while now
2025-02-25 18:39:42 <f_> /whois matrix_ds
2025-02-25 18:39:58 <invoked> ah, i was just going by what anarcat mentioned
2025-02-25 18:39:58 <f_> https://wiki.debian.org/Teams/DebianSocial/Matrix
2025-02-25 18:40:06 <f_> > If you have an IRC room that you would like bridged to Matrix. You can request it using the following link and choosing the add-matrix-pumbed-room template:
2025-02-25 18:40:11 <f_> > https://salsa.debian.org/debiansocial-team/sysadmin/accounts/-/issues/new
2025-02-26 13:40:15 <clandmeter> mio: thanks for the mr. 
2025-02-26 13:40:28 <clandmeter> sorry to cause some design trouble :)
2025-02-26 13:40:39 <clandmeter> btw, didnt you mention you prefered git.a.o urls? 
2025-02-26 13:42:11 <mio> clandmeter: yw, thanks for reviewing and offering feedback!
2025-02-26 13:43:06 <mio> no worries about the design trouble, probably misinterpreted, but think finally got the message
2025-02-26 13:43:43 <mio> yes, it's faster and works more reliably for viewing package history
2025-02-26 13:44:21 <mio> if linking to both is an option that works for me too
2025-02-26 13:44:30 <mio> both gitlab.a.o and git.a.o
2025-02-26 13:53:13 <clandmeter> i guess we could insert two buttons or just text linking to both gitlab and cgit
2025-02-26 13:58:51 <mio> there are two git repo links, next to "Commit" and "Git repository"? for "Commit", maybe the commit hash could be shortened, "2e33b57 (GitLab) / 2e33b57 (cgit)" ... what do you think the links should look like?
2025-02-26 13:59:28 <mio> for "Git repository", "GitLab / cgit"?
2025-02-26 14:01:13 <mio> if the commit hash is displayed in full for link text, guess they could be on a new line within the same cell
2025-02-26 14:01:42 <mio> 2e33b57d112e3df07cc52b94783ce920d2cc09ba (GitLab)
2025-02-26 14:01:47 <mio> 2e33b57d112e3df07cc52b94783ce920d2cc09ba (cgit)
2025-02-26 14:03:40 <mio> or s/cgit/git/ to be consistent with the name used in the right top navigation menu to refer to cgit
2025-02-26 14:07:00 <mio> can open a MR, or if you prefer to add it directly that would be great, thanks
2025-02-26 14:11:41 <mio> whichever works for you
2025-02-26 14:43:53 <clandmeter> you can also just link to cgit
2025-02-26 14:43:57 <clandmeter> we already have the MR link
2025-02-26 16:03:49 <mio> okay, wasn't sure if there were people who preferred gitlab, in which case didn't want to replace what is already there
2025-02-26 16:04:48 <mio> clandmeter: ^ and thanks, will open a MR then
2025-02-27 08:48:18 <ikke> ..
2025-02-27 09:20:09 <ikke> Sorry, this is a repeat message for the previous runnera
2025-02-27 09:20:13 <ikke> runners 
2025-02-27 09:20:18 <ikke> Need to clean them up
2025-02-27 18:37:46 <durrendal> ikke: you had mentioned k8s as a possibility for managing the infra. When we spoke about that was there a specific flavor you were thinking of? I've been dabbling with k3s to familiarize myself with it since I've never used k8s before.
2025-02-27 18:40:21 <ikke> durrendal: k0s
2025-02-27 18:40:38 <ikke> In fact, I already have a cluster running it
2025-02-27 18:41:58 <durrendal> I noticed the k0s adoption MR so that's what I thought
2025-02-27 18:42:26 <ikke> ncopa is working on k0s
2025-02-27 18:42:33 <durrendal> I just setup a k3s cluster in my homelab the other night. I'll put together a k0s cluster next so I'm on the same page
2025-02-27 18:43:28 <durrendal> Oooh I wasn't aware of that, makes a ton of sense to use it then!
2025-02-27 18:43:30 <ikke> Should be really easy (look at k0sctl)
2025-02-27 18:43:47 <fossdd[m]> yes also had nice and easy experience with k0s
2025-02-27 18:44:34 <durrendal> it looks incredibly simple, and I was already under the impression that k3s was easy to deploy and use
2025-02-27 18:44:59 <durrendal> looks like after the initial deployment it's all the expected kubectl workflows as well
2025-02-27 18:47:00 <ikke> yup
2025-02-27 18:54:08 <durrendal> interesting, the k0sctl communication operates over ssh
2025-02-27 18:54:26 <durrendal> just skimming the docs, it looks like a fascinating project, can't wait to tinker with it :)
2025-02-27 18:54:31 <durrendal> thanks ikke!
2025-02-27 19:12:11 <ikke> Testing updating the cluster with k0sctl now 
2025-02-27 19:19:16 <ikke> upgrade succeeded, nice
2025-02-27 19:31:55 <durrendal> \o/
2025-02-27 19:32:30 <durrendal> any thoughts to packaging k0s itself in alpine, or does it seem more reliable to use the bootstrap method that's documented for the project?
2025-02-27 19:34:09 <ikke> You probably want a consistent version of k0s for each node
2025-02-27 19:34:27 <ikke> If we upgrade k0s in aports, then new nodes would get a newer version
2025-02-27 19:44:04 <durrendal> that's a fair point, and then you'd be forced to update those nodes prior to deployment which might not be feasible
2025-02-27 23:07:52 <iggy_> fwiw, I've been using k0s for close to 2 years now and haven't had any issues with upgrades or anything really
2025-02-28 17:50:37 <ncopa> seems like freedesktop are moving their gitlab to kubernetes on hetzner: https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/2076
2025-02-28 18:37:42 <pj> from what I know, they were already on k8s so it's just moving to different service provider